Business Sign-off & Approvals for Jira Cloud
This page is the detailed inventory for Business Sign-off. It is for evaluators, Jira administrators, and technical reviewers who want a structured list of what the Cloud app supports.
It is intentionally denser and less sales-oriented than the product details page. If you want the high-level product story, use that page first.
The core approval experience is designed to be usable for everyday Jira teams while still supporting more formal review flows.
Use lighter or stricter controls depending on how much governance the process needs.
Built-in controls help reduce self-approval and conflict-of-interest risk.
Prevent issue reporters from acting as approvers when that control is required.
Prevent assignees from approving their own work when needed.
Re-check SoD when assignee or reporter changes so risk does not stay hidden after issue edits.
Use global defaults or let projects override SoD settings where appropriate. The admin guide covers how the Cloud configuration model is set up.
The app can operate as a lightweight issue-level approval tool or as a true workflow control layer inside Jira.
Notification features are designed to keep approvals moving without overwhelming users.
Notify approvers when they are added or when review is requested.
Notify pending approvers or reset decisions and request re-review when work changes.
Prevent repeated notifications to the same approver within the same day.
Notify issue requestors and assignees when approvals are recorded or when approval passes or fails.
Approval data is designed to support review, oversight, and audit evidence gathering.
For supporting implementation and security detail, see the trust and security page.
Approval data is not trapped in the UI. It can support search, dashboards, and automation use cases across Jira.
Read-only Jira field showing current approvers on the issue.
Read-only Jira field showing the overall approval state.
Search by approver or approval state using Jira-native querying. Configuration and usage details are covered in the admin guide and user guide.
Approval metadata is stored in Jira issue properties to support deeper integration and reporting patterns.
Beyond approval controls, the app includes privacy-oriented features that matter during security and compliance review.
Support for Atlassian’s personal data reporting model.
Administrative reporting on where account data is referenced inside app records.
Closed-user records can be pseudonymized to support privacy obligations.
Approval data remains within Atlassian-managed Jira Cloud and Forge infrastructure. More detail is available on the trust and security page.
Use the product details page for the higher-level overview, or browse the docs and trust and security page for deeper admin and evaluation detail.