Release notes

Version 6.1.0 — Outcome recording

Released 30 October 2026

New Features

• Record a change on the Jira issue. Choose which issue types are governed and those issues gain a Concessa panel with a summary, risk level, change type, impacted service and planned window. Nothing is copied into a second system, and nothing leaves your Atlassian site.
• Ask for approvals and answer them, with the role each approver is speaking for. Nobody can approve their own change.
• Declare freeze windows and see them on the change calendar. A change scheduled into a freeze cannot be approved until it is rescheduled or an administrator records an override with a reason. A change can be overridden once per freeze window.
• Record what happened to an approved change: implemented, backed out, fixed forward, failed or not carried out. Where a change calls for it, add a short post-implementation review.
• See a warning on the panel when an approved change’s window has passed with no outcome recorded. A change carried out without approval can be declared as such, after a confirmation that says what that means.
• Run a change advisory board. Set a schedule and a standing agenda, build each meeting’s agenda from the changes awaiting review, and record attendance, actions and outcomes.
• Export the evidence for a project or a single change as CSV and JSON, with the audit trail and a check that the audit chain is intact. Whole-project exports now include every outcome and a set of measures over a period you choose.
• See when Jira Service Management’s planned and actual dates differ from the change’s planned window. The panel offers to copy Jira’s dates into the form and never changes them by itself.
• Publish change status to the Jira issue so it can be searched with JQL. It is off by default for every project and is turned on by a project administrator. Turning it on publishes the project’s existing change records.

Improved Features

• The buttons that move a change record now read Move to Approved and Move to Rejected, so they cannot be mistaken for the Approve and Reject an approver uses to answer their own request.
• Every place that judges a freeze now says that Jira Service Management’s own freeze windows are not included, and the evidence export says so too.
• Every question in the outcome forms and on the evidence page is a labelled field that a screen reader announces by name, and every text field states its limit before you type.
• If Jira refuses a comment, the action you took is still saved and the panel tells you the comment was not posted.

Security Fixes/Patches

• On Jira Service Management projects, Concessa’s comments are now internal, so the customer portal does not show them. Your Atlassian site administrator is asked to approve one additional permission for this.
• Withdrew the saved search function that listed changes awaiting one named person’s approval. Jira can reuse a function’s answer for other people, so it could show that list to other approvers.

Defect Fixes

• A rejected change can no longer be turned back into an approvable one by rescheduling it into a freeze window.
• A change with a rejection now says so, instead of reporting that approvers have not answered yet.
• Overriding one freeze window no longer silently excuses a second freeze window over the same dates.
• Declaring or deleting a freeze window now updates the published status of the affected changes.
• A change that has reached its approval limit now has its approvals withdrawn in one step when it is rescheduled.
• Turning on publishing for a project now publishes its existing change records straight away, instead of waiting for the nightly repair run.
• A change record whose Jira issue has since been deleted is no longer reported as a failed publish on every repair run. The settings page now reports it as skipped.