Hi Smitty — short answer: there is no built-in "sign off" field in Jira, so there's no single field change to watch for. "Sign off" is always something your instance has been configured to mean, and the right Automation trigger depends on which of these it is. Rather than guess, here are the four common shapes and the trigger for each — one of them will match your setup:
1. It's a workflow transition (e.g. a "Sign off" or "Approve" button moving the item to Signed Off / Approved). Most common by far. Use Work item transitioned, with From/To set — leave From blank and set To = your signed-off status. This is more precise than "Field value changed → Status," because it lets you distinguish which path was taken into the status.
2. It's a JSM/approval step. If the item type has an approval configured, use the Approval required / Approval completed triggers rather than watching a field. {{approval.decision}} gives you approved vs. declined, and {{approval.approvers}} the people.
3. It's a custom field — an "Approver", "Signed off by" user field, or a "Sign off" checkbox/select someone added. Use Field value changed, pick that specific field, and set "Change type: Value added/changed" so you don't fire on it being cleared. If you're unsure the field exists, Admin → Issues → Custom fields and search "sign" will tell you in ten seconds.
4. It's a comment or attachment convention (someone posts "signed off" or attaches an approval doc). Use Work item commented with a condition on {{comment.body}} containing your phrase — fragile, but it's what some teams actually do.
Fastest way to identify which one you have: open an item that's already been signed off, click History, and look at the entry created at the moment of sign-off. Whatever changed there — Status, a custom field, an approval entry — is your trigger. If nothing changed in History, it's the comment/attachment case.
One Data Center note: if you land on Field value changed, be aware the rule fires on the field changing to anything, so add a condition on the new value, otherwise you'll get runs on every edit and clear.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.