User guides
Concessa user guides: from install to audit, step by step
Ten short guides covering every change management workflow Concessa supports in Jira and Jira Service Management, in the order you will need them. Each one is a complete task with the screens you will see along the way.
There are two roles, both from Jira
| Role | How you get it | What it lets you do |
|---|---|---|
| Project administrator | Hold Jira’s Administer projects permission on the project | Everything an agent can do, plus configuration and recording a freeze override |
| Agent | Be a member of any Jira project role an administrator bound — directly or via a group | Record changes, request and answer approvals, read every view, take exports |
An administrator is always an agent too, whether or not a role has been bound and whether or not they are in it. That is deliberate: otherwise the first person to open the app could not get in.
Anybody else — a licensed Jira user in the project who is in none of the bound roles — sees the Concessa surfaces but no governance data, only an explanation of who can grant them access. JSM portal customers see nothing at all; Concessa has no portal surface.
Where Concessa lives in Jira
Three surfaces, and no others:
- The issue panel, named Concessa, on a Jira issue. This is where a change record lives.
- The project page, named Concessa, with three tabs: Change calendar, CAB workbench, and Evidence. All three share one address — Jira allows an app a single project page, so a link to “the CAB workbench” is a link to the project page.
- Project settings → Concessa, for administrators only.
Three things worth knowing before you start
A change record is a Jira issue. Concessa does not keep a separate list of changes. It adds governance data — a summary of the change, its risk, change type, impacted service, planned window, status and approvals — to an issue that already exists, so your changes stay searchable by JQL, visible on boards, and subject to the project’s own permissions.
The audit trail cannot be edited or deleted. Every governance action appends an entry to a hash-linked chain, and there is no path in the product that removes one. This is what makes the export evidence rather than a report — and it is why starting a change record on the wrong issue is worth avoiding rather than undoing.
Nothing leaves your Atlassian site. Concessa makes no outbound call of any kind. That is why the evidence export is text you copy rather than a file you download: producing a download would mean sending your governance record somewhere to be turned into one.
The ten guides
- 1 Administrator setup Bind the agent roles, nominate the issue types that count as changes in your Jira project and, if your board meets on a cadence, set the CAB schedule. Project administrator 3 min
- 2 Recording a change in Jira Bring a Jira issue under change governance: what is changing, its risk, change type, impacted service and planned window, and why there is no Standard type. Agent 4 min
- 3 Change approvals in Jira Ask a named agent to approve a change in Jira, answer a request addressed to you, and see why a decision is final and covers only the dates it was given for. Agent 4 min
- 4 The governance lifecycle Five statuses, the moves you can make between them, the five the system makes for you, and what has to be true before a change can be approved. Agent 3 min
- 5 Freeze windows in Jira Declare a change freeze in Jira, see what it catches, backwards as well as forwards, and record an override bound to the window it excuses. Project administrator · Agent 4 min
- 6 The change calendar See a month of Jira changes as risk-coloured blocks across their planned windows, which days are frozen, and which sit in a freeze nobody has overridden. Agent 3 min
- 7 The CAB workbench in Jira The change agenda for your change advisory board: every change record in the Jira project, in review order, with five filters that carry their own counts. Agent · CAB chair 3 min
- 8 CAB meetings and actions The board’s own record in Jira: meetings created from a schedule, attendance and agenda, what holding a meeting seals and posts, and the actions it raised. Agent · CAB chair 5 min
- 9 Evidence and the audit trail Read the hash-linked audit chain, take an evidence export from Jira for an auditor, and know exactly what it proves and what it does not. Agent 4 min
- 10 Troubleshooting Every message Concessa can show you in Jira, what it means and what to do, plus the things people expect that do not exist. Everyone 6 min
Put change governance where the work already happens
Concessa is a pure Forge app, charged per agent. No external systems, no data leaving your site, nothing to host. Install it from the Atlassian Marketplace.