Release Notes

New and improved

• The My Approval Queue dashboard gadget now shows the same “unresponsive approver” indicator already available on My Approval Requests.

Security and privacy

• Workflow validators that require approvers now correctly block a transition when they’re unable to confirm approval status due to an unexpected error, rather than allowing it through by default.
• Strengthened an internal permission check as an additional precaution. This did not affect any user-facing feature or require any action.

Fixed

• A compliance audit export covering a date range with more than 100 matching issues could return only a partial result with no indication anything was missing. Date range exports now return the complete matching set.
• In rare cases, two approval actions recorded on the same issue in very close succession could cause one of them to be dropped from the compliance audit trail. This has been corrected.
• Resolved a timing issue where the automated reminder sweep could temporarily revert an approver’s decision if it was recorded while a batch of reminders was still being sent, or could re-send a reminder a second time after an earlier attempt partially failed.
• The automated reminder sweep could, in a rare failure case, lose its own record that a reminder had been sent, even though the reminder email itself had gone out. The record is now preserved.
• The automated reminder sweep and the manual Notify Approvers action now both correctly stop reminding approvers once an issue is marked Done or its approval outcome has already been decided.
• Corrected an issue where a security scheme granting access to “the current assignee” or “the current reporter” of an issue was not recognized, which could incorrectly prevent that person from being added as an approver.
• If cleanup of a deleted Jira project’s data encountered an error partway through, the rest of that project’s data could be left behind indefinitely. Cleanup now continues past an individual error.
• Corrected a timezone calculation that could file Admin Audit Log and audit export date-range results under the wrong calendar day on the two days per year clocks change for daylight saving time.
• Corrected an issue where selecting a custom date range on the Admin Audit Log could report no matching entries for administrators in timezones ahead of UTC, even when matching entries existed.
• Internal notification logs now correctly distinguish a notification that was actually delivered from one Jira refused to send.
• The Remove Approvers workflow action no longer defaults to removing every approver on an issue if an administrator saves it without choosing a specific option. An option must now be explicitly selected.

Upgrade

• No action required. No configuration changes are needed, and saved settings are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.
• Administrators configuring the Remove Approvers workflow action must now explicitly choose a removal option before saving; it no longer defaults to removing everyone.
• Issues using a security scheme that grants access to “the current assignee” or “the current reporter” will now correctly show that person as eligible to be added as an approver, where they may have previously been excluded.
• Notify Approvers will no longer run on an issue that is already marked Done, matching the existing behavior for adding or removing approvers.
• A date range audit export that previously returned a partial result for a large match will now return the complete result when re-run.
• Admin Audit Log and audit export date-range results for the two days per year affected by daylight saving transitions will shift by one hour and be accurate going forward.

Fixed

• Removed internal debug and testing tools that were inadvertently left visible on the Admin page’s General tab after a previous release’s testing phase. These tools required Jira administrator access and were never reachable by non-administrator users.

Upgrade

• No action required. No configuration changes are needed, and saved settings are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.
• Administrators who previously saw labeled "DEBUG" controls on the Admin page’s General tab will no longer see them. Nothing else on that page changes.

Security and privacy

• Approver eligibility now also accounts for issue-level security restrictions, not just project-level access. A user excluded from a specific issue by its security level can no longer be surfaced or added as an approver on that issue.
• Corrected a permission-checking issue that could, in a narrow timing window, allow an Add, Remove, or Notify Approvers action to succeed in an already-open issue panel after the acting administrator’s access had been revoked, if that panel was not reloaded first.

Fixed

• Corrected a timing issue where a decision recorded around the same time automated reminders were being processed could, in rare cases, be temporarily reverted in storage, even though the approval history correctly showed the decision. A reminder is also no longer sent a second time for the same due cycle if the same reminder is processed more than once.
• Extended the same protection to the approver wait-time pause and resume process, so a decision made at the same moment an issue’s workflow status changes is no longer at risk of being temporarily overwritten.
• Corrected a rare timing issue where two overlapping scheduled reminder runs could both process the same due approvers, which could result in a duplicate reminder.
• Corrected a rare timing issue where adding two approvers to the same issue in close succession could leave one approver temporarily missing from that issue’s approver list, even though their approval record existed. This is now automatically detected and corrected.
• Corrected a rare delivery issue where reprocessing an audit export could send a duplicate “export ready” email, or in rare cases include stale data in the downloaded file.
• Corrected an issue where frequent manual use of Notify Approvers could prevent an unresponsive approver from ever being flagged, even once the configured reminder interval had been exceeded.

Upgrade

• No action required. No configuration changes are needed, and saved settings are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.
• One behavior change to be aware of: a user excluded from an issue by its issue-level security scheme can no longer be added as an approver on that issue, even if they otherwise have project-level access. This closes an unintended gap rather than introducing a new restriction.

New and improved

• Automated Email Reminders for approvers who haven’t acted on a pending approval, including an optional notice when an approver becomes unresponsive. Ships off by default.
• The Admin and Project Settings pages are now organized into tabs, with email notification settings consolidated and configurable site-wide with per-project override.

Fixed

• Notify Approvers could fail silently when an approver’s Atlassian account had been deleted while still Pending, with no indication in the app that the approver was unreachable. The issue panel now flags a deleted approver, and Notify Approvers skips them cleanly instead of failing — the same account check applies to Automated Email Reminders.
• A workflow transition requiring approvers could be blocked on an issue type that a project had excluded from Business Sign-off, even though that issue type was never meant to need approvers. Excluded issue types are no longer blocked.
• Deleting a Jira project now reliably removes that project’s approver records and audit history, rather than potentially leaving them behind in storage indefinitely.
• A rare, transient failure reading stored data or calling Jira’s API is now retried automatically rather than silently aborting the operation.

Upgrade

• No action required. No configuration changes are needed, and saved settings are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.
• Automated Email Reminders ships off by default. Turn it on in Business Sign-off → Notifications, globally or per project. The Unresponsive Approver notice also ships off by default for each recipient, and can be turned on independently once automated reminders are in use.
• The Admin page and Project Settings page are now organized into tabs. Every setting keeps its previous value and grouping — only the navigation changed.

Fixed

• Further improved synchronization of BSO - Approvers and BSO - Status for JQL searches and dashboard reporting.
• Approval assignments, decisions, and audit history were unaffected by the reporting-field issue.

Upgrade

• No action required. No configuration changes are needed, and saved settings are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.
• JQL syntax, saved filters, and dashboard gadget configuration are unchanged.

Fixed

• Corrected a synchronization problem that could leave BSO - Approvers and BSO - Status showing stale or missing information in JQL filters and dashboard views, most often on a newly installed site.
• Approval assignments, decisions, and audit history were unaffected.

Upgrade

• No action required. No configuration changes are needed, and saved settings are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.

New and improved

• Approver waiting-time clocks now pause when an issue leaves an active workflow status, such as when work is put on hold or blocked, and resume when it returns to an active status.
• Paused is now a searchable BSO status. Use "BSO - Status" = "Paused" in JQL.
• The issue panel, My Approval Queue, and My Approval Requests show a Paused badge on affected approvers.
• If an already-paused clock needs to resume, it can still resume after the pause feature is turned off. Turning the feature off prevents new pauses.

Security and access

• Notify Approvers now requires the same approver-management permission as adding or removing approvers. Users without that authority can no longer notify approvers through a less restrictive check.
• All Users eligibility now selects users with Browse Projects access to the issue’s project. Approvers who lose that access after being added are flagged in the panel.

Fixed

• The Admin Audit Log now reliably shows the most recent entry first, and its default filters find matching entries that were previously missed.
• Customized issue-type icons display correctly in both dashboard gadgets.
• Add Approver, Decision, Notify, and History dialogs no longer retain unsaved input from a previous opening.
• Saving global or project settings now reports a conflicting change by another administrator and offers the option to reload the latest configuration before trying again.
• BSO - Status and BSO - Approvers now display consistently in Jira’s issue Details panel.
• Corrected a browser-console error when opening administrator or project settings. No impact on approvals, notifications, audit data, or other functionality was observed.
• Workflow post-function selection menus no longer cut off or overlap options.

Behavior and upgrade

• Pausing waiting-time clocks is enabled by default. Wait-time figures now exclude periods outside an active workflow status.
• Teams that prefer the previous always-running clock can turn the feature off in Business Sign-off → Settings, globally or with a project override.
• Projects using All Users may see fewer candidates in the Add Approver picker because candidates must have the documented project access.
• No configuration changes are required, and saved setting values are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.

New and improved

• Audit CSV exports now offer Issue List mode alongside Date Range mode. Issue List exports retrieve the complete approval history for the specified issues, regardless of when the events occurred.
• Issue List mode accepts up to 50 issue keys per export, supporting audit samples selected using Jira search.
• Exports now offer Include Integrity Verification, enabled by default and adjustable for each export. Results report detected changes to audit records and distinguish legitimate privacy redactions from unexplained changes.
• Approval history now records changes to an issue’s overall approval outcome, including changes away from Approval Passed or Approval Failed after an approver is removed.
• Overall-status events appear in Audit History and CSV exports with readable status labels.
• Added feature-usage counters within Atlassian’s infrastructure.

Fixed

• Administrator and workflow configuration screens no longer briefly display raw label text when opened.
• Audit History remains accessible when an issue has history but no current approvers.
• Exports explicitly state when no records match the selected criteria.
• Approver actions no longer cause repeated panel refreshes and flicker.
• Corrected inconsistent output in a decision-related CSV export column.

Behavior and upgrade

• Integrity verification is included by default; clear Include Integrity Verification for an export if it is not needed.
• Audit History remains available after all approvers are removed, and overall-outcome changes generate additional history entries.
• No configuration changes are required, and saved setting values are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.

Security and privacy

• Audit export tools, including starting, viewing, and deleting exports, now require Jira administrator permission. Related project searches in administrator tools have the same requirement.
• Issue-specific actions and lookups verify the caller’s permission to view the issue before returning data.
• Decision recording checks Edit Issues permission at the issue level rather than only at the project level, addressing projects with issue-level security.
• Dashboard and export project selections are validated more strictly to prevent requests from returning a wider set of issues than intended.
• Corrected an authorization issue that could apply another user’s administrator permission state to a request.
• Separate placements of the same dashboard gadget no longer share configuration unexpectedly.
• CSV exports protect against spreadsheet formula execution when opened in Excel, Google Sheets, or LibreOffice.
• My Approval Queue now receives issue summaries limited to 50 characters, reducing the issue content included in gadget responses.
• Clarified the audit-integrity documentation: the checks described for this release detect accidental corruption or casual editing; they do not make records immutable or prevent users with Edit Issues permission from changing the underlying Jira data. Trust & Security is the reference for the capability and its limitations.

Fixed

• Audit exports containing large amounts of non-English text, including Japanese, Cyrillic, and other non-Latin scripts, now complete normally.
• Invalid decision values are rejected with a clear error instead of being recorded and affecting approval reporting.

Behavior and upgrade

• Audit CSV export is restricted to Jira administrators. Users without that authority can no longer access the export tools.
• No configuration changes are required, and saved setting values are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.

New and improved

• The issue panel’s Add Approver dialog supports selecting and adding several people in one action.
• If only some selected approvers can be added, the dialog keeps the selection and identifies those who were not added.
• An approval remains Awaiting Decisions while its threshold is still reachable. A Returned decision no longer immediately marks it as failed when remaining approvers can still meet the threshold.
• This status change affects thresholds below 100%. At the default 100% threshold, one Returned decision still settles the outcome as failed.
• Audit History shows Max Possible when an approver has returned, helping users understand whether the threshold remains reachable.
• Workflow removal of an approver now sends outcome emails when the removal changes the overall result, following the separate Email Reporter on Approval Outcome and Email Assignee on Approval Outcome project settings.
• Removal history and CSV exports now include the removed approver’s decision at the time of removal. Panel and workflow removals record consistent information.
• Refused approver actions now explain why they cannot proceed, including restrictions when an issue reaches Done, rather than suggesting an ineffective retry.
• Workflow resets and filtered approver operations are faster on issues with many approvers.

Fixed

• Reporter and assignee outcome emails are sent when an outcome is reached, and again only if it genuinely changes, rather than after every subsequent decision.
• When notifying approvers partly succeeds, history records those successfully notified.

Behavior and upgrade

• Projects with thresholds below 100% may see fewer approvals marked as failed because reachable approvals remain Awaiting Decisions.
• Workflow removals may now send outcome emails where none were previously sent. Review the existing notification settings in Project settings → Business Sign-off if you want different recipients.
• No configuration changes are required, and saved setting values are unchanged.
• No new OAuth scopes or permissions; no administrator re-approval is required.

New and improved

• Workflow reset emails identify the issue’s new status and explain the reset without asking recipients to review work that may have been paused or parked.
• Reset Approval Status notifies affected approvers by default. Explicitly disabled notification settings are preserved.
• Automated workflow actions appear as System in approval history and CSV exports.
• Reset-notification history identifies the approvers notified instead of only showing a count.
• Project settings labeled Email Requestor on … are now labeled Email Reporter on …, matching Jira’s Reporter field. Saved values are unchanged.
• Reset transitions on issues with many approvers complete faster.

Fixed

• Active subscriptions no longer show a misleading expiry countdown. A notice remains for genuinely expired licenses.
• Approvers added through the Add Approvers post-function receive the added-approver email when Email Approver When Added is enabled, and the additions appear in approval history.
• Workflow resets are recorded distinctly from manually requested re-review.
• Notification history records send outcomes, including refused delivery.
• Configuration history displays option names matching the settings screens.
• Corrected personal-data reporting so non-user system activity is not reported to Atlassian as a user account.

Behavior and upgrade

• A Reset Approval Status post-function configured before notification became an option now notifies the approvers whose decisions it resets.
• Post-functions with notification explicitly turned off remain unchanged. To change notification behavior, edit the post-function in the workflow editor.
• No configuration changes are required. Saved values are unchanged; the Reporter rename changes labels only.
• No new OAuth scopes or permissions; no administrator re-approval is required.

New and improved

• Reset Approval Status supports resetting all decisions, Returned decisions only, or Approved decisions only.
• Reset all decisions remains the default, matching previous behavior.
• Role/group filters can be combined with decision-status filters in the same reset post-function.
• Only the approvers included in a filtered reset receive its notification, and the message describes the reset performed.
• Returned-only resets can support phase-gate workflows with Decision Locking, clearing earlier returns without disturbing carried-forward approvals.
• Selective Reset is marked deprecated in the workflow editor. Existing configurations continue to work; use Reset Approval Status for the combined options.
• Issue-type eligibility is enforced consistently when adding approvers through the panel or workflow.
• If an issue already has approvers when its type becomes ineligible, the panel remains available for existing decisions, resets, removals, and administrator cleanup. A banner explains that new approvals are no longer allowed.

Fixed

• Expanding an Admin Audit Log entry after filtering or sorting no longer shows details belonging to a different entry.

Upgrade

• No configuration changes are required.
• Existing Reset Approval Status and Selective Reset configurations continue to work without edits. New reset modes and filters are opt-in.
• No new OAuth scopes or permissions; no administrator re-approval is required.

New and improved

• BSO - Approvers and BSO - Status are now locked, app-managed fields. Jira’s Fields administration shows a LOCKED indicator and does not offer Edit or Delete for these fields.
• Both fields are created automatically during app installation and are available for JQL, issue-navigator columns, dashboards, and the approval panel.
• Existing installations retain their field identifiers and values.

Upgrade

• No action required. Field management changes apply automatically without data migration or manual field setup.
• No new OAuth scopes or permissions; no administrator re-approval is required.

Improved

• The panel and both dashboard gadgets load faster for issues, projects, and users with large approver lists.
• Add Approvers workflow operations complete faster when adding large roles or groups, particularly selections of 15 or more approvers.
• Gadget auto-refresh is more reliable under heavy use.

Fixed

• Corrected delivery of the weekly personal-data report to Atlassian.
• The panel does not render for a deleted issue or an issue the app can no longer read, instead of producing an error for that condition.

Upgrade

• No customer action is required for the personal-data reporting fix; reporting resumes on the next scheduled weekly run after upgrading.

Improved

• The entire Business Sign-off panel, including its header, is hidden on projects where the app is disabled.
• Projects in finishing mode retain the panel so existing approval work can continue.
• This visibility improvement applies to Jira Software, Jira Service Management, Jira Work Management, and Jira Product Discovery.
• Resolves the disabled-project panel-header limitation documented in version 1.0.0.

Permissions and administrator consent

This release adds:

• write:project.property:jira
• delete:project.property:jira

These permissions support project-level panel visibility. Site administrators must approve the new permissions before the upgrade applies.

Required upgrade action

Previously enabled projects need a one-time settings save to restore panel visibility after the upgrade:

1. Approve the updated app permissions when prompted.
2. For each enabled project, open Project settings → Business Sign-off and click Save.
3. Reload the issue to display the panel.

Previously enabled projects may otherwise lose their panel on the next issue load. Approval data is not lost.

Visibility changes appear on the next issue load or refresh; already-open tabs do not update immediately.

New: My Approval Queue

• Shows open issues where you are an approver.
• Filter by approver status: Added, Pending, Approved, Returned, or All.
• Filter to a project or include all projects.
• Choose 10, 25, 50, or All results per page.
• Choose no automatic refresh, or refresh every 15 minutes, 30 minutes, 1 hour, or 2 hours.
• Shows issue type, key, summary, issue status, your decision, decided-approver count, and days in the current status.
• For closed-issue or historical reporting, use JQL with the BSO custom fields.

New: My Approval Requests

• Shows open issues where you are the reporter, assignee, or either, and which have approvers.
• Filter by approval state: Open (Not Started and Awaiting Decisions), Returned, Approved, or All.
• Filter to a project or include all projects.
• Choose 10, 25, 50, 100, or All results per page.
• Choose no automatic refresh, or refresh every 5 or 15 minutes.
• Shows issue type, key, summary, issue status, BSO status, decided-approver count, and days in the current status.
• Expand rows to view approver status, decision date, and waiting time. Open the issue to read full decision comments.
• Issues without approvers are excluded.
• If more than 500 matching in-progress issues are found, a truncation banner asks you to refine the filters.

Gadget behavior

• Saved configurations survive dashboard reloads, browser sessions, and app updates.
• Editing a gadget opens its saved values; defaults apply on first configuration.
• Both configuration forms offer Cancel without saving.
• Auto-refresh keeps the existing table visible during reload.
• Inactive-license messages are displayed more prominently.

Fixed

• Panel actions reflow within narrow issue-detail columns instead of being clipped. Wide-column layouts are unchanged.
• Ineligible approvers retain their Added, Pending, Approved, or Returned status label and display a separate eligibility indicator with the reason.
• Eligibility indicators are also shown for previously decided approvers who later become ineligible.
• Existing approval and permission rules are unchanged by these display fixes.

Improved license-expiry behavior

• Existing approval work can continue with an inactive license when the project is in finishing mode, including recording, withdrawing, or resetting decisions.
• Adding new approvers and other new-work operations remain restricted until the license is renewed.
• The issue panel more clearly explains finishing-mode restrictions and offers appropriate messages for an ended trial versus an expired paid subscription.
• Decision and Notify Approvers controls reflect the in-flight permissions.
• If a license expires during an open decision dialog, the message explains the license restriction instead of showing a generic error.

Data access

• Personal-data reports remain available regardless of license state.
• Audit-history exports and export cleanup remain available regardless of license state, supporting access to existing compliance evidence.

Fixed

• Notification actions handle cases with no recipients, including missing reporter or assignee recipients. Notifications with valid recipients are unchanged.
• Corrected a failure in personal-data reporting to Atlassian.
• Deleted issues no longer produce unnecessary warnings during reporting-field updates. Issue-deletion cleanup is unchanged.

Approval management

• Add, remove, and notify approvers from the issue panel.
• Approve, Return, and withdraw decisions, with optional or required comments.
• Configure percentage-based approval thresholds and view Not Started, Awaiting Decisions, Approval Passed, and Approval Failed.
• Notify new approvers, remind undecided approvers, or request re-review with decision resets.
• Optionally lock approved decisions after the issue moves to another workflow status.
• Require comments for all decisions, approvals only, returns only, or neither.

Administration and permissions

• Manage global settings and project-level overrides for thresholds, Separation of Duties, eligibility, comments, and decision locking.
• Configure whether the reporter, assignee, and/or Jira administrators can manage approvers.
• Restrict approvers by project roles and groups.
• Apply Separation of Duties rules to prevent reporter or assignee self-approval, with re-evaluation when those fields change.
• Optionally require Edit Issues permission to decide.
• Limit panel visibility to standard issue types, excluding subtasks, or selected issue types.
• Use finishing mode when disabling the app to preserve existing approval work while preventing new work.

Workflow integration

• Conditions and validators enforce approval requirements on transitions, with configurable validation messages.
• Post-functions add approvers from users, roles, groups, or custom fields; remove approvers; reset decisions; and send notifications.
• Selective Notify and Selective Reset support role/group filters.
• Notification rate limiting helps prevent duplicate reminder notifications.

Audit and reporting

• View approval history with participant, action, time, comment, and Separation-of-Duties context.
• Approval history includes record-integrity information. Version 1.4.1 clarifies integrity limitations; version 1.5.0 adds optional verification to exports.
• Export approval history to CSV using project and date-range filters, with progress tracking.
• Review configuration changes in the Admin Audit Log, including who changed settings and when.
• Enable time-bounded diagnostic logging for troubleshooting, with automatic expiry after the configured 1–8 hours.
• Read-only BSO - Approvers and BSO - Status fields support issue columns, dashboards, and standard JQL. For example, "BSO - Approvers" = currentUser() and "BSO - Status" = "Approval Passed".
• Approval statistics support advanced issue-property queries.

Notifications

• Configure project-level emails for approval requests, decisions, outcomes, and re-review.
• Decision and outcome notifications can be sent to the reporter and/or assignee.

Privacy and licensing

• Reports stored account identifiers to Atlassian on a weekly schedule and pseudonymizes stored records when Atlassian reports a closed account.
• Administrators can request a personal-data report.
• App data stays within Atlassian infrastructure rather than being transmitted to external services.
• Marketplace licensing supports trials and displays license state in the administrator page and issue panel.
• License restrictions preserve read access to existing approval data. Version 1.0.2 documents the later finishing-mode and data-access changes.

Permissions at initial release

The initial release documented these scopes:

• storage:app
• read:jira-work
• write:jira-work
• read:jira-user
• manage:jira-configuration
• write:app-data:jira
• report:personal-data

Version 1.2.0 adds project-property permissions and requires administrator approval.

Limitations at initial release

• BSO custom fields are read-only. Manage approvers through BSO actions rather than editing field values directly.
• The panel header remains visible on disabled projects even when the body is empty. Version 1.2.0 addresses this limitation.
• Rapid successive operations may occasionally show stale information.
• The first load after inactivity may take longer.