Can Jira make sure a named person signs off a ticket before it moves to the next status? In Jira Service Management, yes: approvals are built in there. In Jira Software and Jira Business projects, as far as I know, there is no native sign-off.
The usual workaround is a status per approver. "Waiting for Legal", "Legal approved", "Waiting for Finance", and so on, with the transition out of each status limited to a person or a group. It works, and for one approver in one project I would not bother with anything else.
It starts to hurt with the second approver. Every new sign-off is another pair of statuses, and parallel approvals turn into a chain, because a ticket can only be in one status at a time. The workflow now says who is next, but not who signed what and when, beyond what you dig out of the history. Nobody can say whether the person who approved also wrote the request. And a ticket edited after approval keeps its approval.
What I wanted was a short list of sign-offs on the ticket itself: each with its own approvers, each recording who signed and when, with the move blocked until the required ones are in. Jira does not have that for software projects, so I built Approval Flow at Stanki Guild. I am biased.
You add requirements to a ticket, name the people who may sign each one, and mark the ones that gate the transition. Until every required sign-off is in, the move is refused with a message that says how many are open. A rejection needs a reason. Editing a requirement's text clears its sign-offs, so an approval always refers to the text that was approved. Named approvers, the audit trail, stages (stage 2 opens only when stage 1 is signed) and "2 of 3 must approve" are in the free edition. Groups and project roles as approvers are paid.
The 3.0 release added two things I would use. One is separation of duties. With it on, the person who set up a requirement cannot sign it, and, new in 3.0, neither can the person who last changed who may sign it. Before, whoever configured a requirement could name themselves and sign. The other is bulk approval. If you owe fifty sign-offs, you can approve them from one screen and enter your PIN or authenticator code once, not once per batch of ten. The code opens a five-minute session that covers exactly the set you selected, nothing else. The code and the bulk screen are both paid.
The newest piece is also paid, and the one I am least sure of. An AI agent can ask a person to approve one concrete action on a ticket before it runs it. The approver reads one plain sentence built from structured fields, not the agent's own wording, and decides with their code. There is no tool that lets an agent approve anything, and the user the agent works for can never approve its request. It is off until an administrator switches it on. I ran the request side on a test site, with the setting off and on. The approver side and the signed receipt are covered by automated tests, but I have not run them on a live site.
I do not know how many of you need this on tickets rather than in a document tool. And an audit trail is evidence, not a verdict: whether it satisfies a control is between you and your auditor. Other approval apps on the Marketplace do similar things.
How do you collect sign-off in Jira today: statuses, comments, or trust?
