Getting started

Install

Lacre is an app for Jira Cloud. A site administrator installs it from the Atlassian Marketplace (once it is published) and it is paid by subscription through Atlassian, like the site's other apps. It runs entirely on Forge, Atlassian's app platform: there are no servers of its own and no separate accounts, and the data stays on Atlassian's infrastructure.

Where it appears

In the view of every issue, Lacre adds the "Lacre" panel next to the other issue details. The panel header shows the state without opening it:

• 0: the issue has no current sealed check.
• A green identifier (L- and ten characters): that of the current check, the latest one sealed.

When opened, it shows the project's checklist, the change risk level, the buttons to seal and, below, the seals of the issue. How to use it: Sealing and approving.

Every project also has its Lacre settings page: in the Jira project settings, the "Lacre" entry. Only project or Jira administrators can see it: Administration.

What it does with no configuration

Lacre works as soon as it is installed, in every project:

• Enabled, with the default checklist: eight items (five required and three optional) about the risk, the tests, the rollback plan and the documentation of the change.
• With no roles: anyone who can see the issue can tick the checklist and seal, and nobody can approve until the project has approver roles.
• In each user's language: the panel is shown in Spanish if the Atlassian profile of the person opening it is in Spanish, and in English otherwise.

The five minutes before the first seal

On the project's Lacre settings page ("Lacre in this project"):

1. The checklist. Review the eight default items and remove, change or add whatever you need (up to twelve, each in Spanish and English, required or optional).
2. Who checks and seals. Choose the project roles that can tick the checklist and seal, for example "Developers". With none, anyone who can see the issue still can.
3. Who approves. Choose the project roles that approve, for example one called "Security Officer". If high-risk changes need an approval before they are carried out, tick "Require prior approval for HIGH risk".
4. Custom fields, if any should be part of the seal (a change request number, a maintenance window).
5. The panel language, if the project's evidence should be in a single language.
6. Click "Save".

Roles are Jira project roles: if there is no role for approvers yet, a Jira administrator creates it and people or groups are assigned to it in the project settings.

Then try it on an issue: tick the items, choose the risk and click "Seal check". The panel header changes from "0" to the seal identifier.

Without an active subscription

If the site's Lacre subscription is not active (the trial ended or it was not renewed), the panel still shows the checklist, the seals and their history, and "Verify" still works, but nothing can be ticked, sealed or approved: instead of the buttons there is a notice with the link "Manage the site apps". The settings page keeps working in full, so the customer can export or delete their data. A seal is never deleted or hidden because of the subscription.

What the app asks for

Lacre only asks for the permissions it needs: reading issues (to seal their state and detect changes), reading users (to confirm who signs and to put names in the export), writing the copy of its seals into each issue and using its own storage. It sends no data outside Atlassian.