Approval emails don’t include the request details
Put cost, access level and justification right in the approval email.
Approvers shouldn’t have to click through to decide. Here is how to give them everything in the email itself.
The symptom
The approval email asks for a decision but shows almost none of the context — cost, access level, requester, justification — so approvers either open the portal or approve blind.
Why Jira Service Management behaves this way
The approval notification template exposes a limited, fixed set of fields and can’t be extended to include the request fields that actually matter to a decision.
The manual workaround — and why it falls short
Teams tell approvers to always open the ticket first, which defeats the point of an email approval and slows every request down.
How Patcher fixes it
Patcher puts the request’s key details straight into the approval email alongside Approve and Decline actions, so approvers decide correctly in one glance.
Turn it on
- Install Patcher for Jira Service Management from the Atlassian Marketplace.
- Open Patcher › Patches from your Jira Service Management admin.
- Find Rich approval emails in the list and switch it on.
- Scope it to the projects you choose, then save — the fix is live immediately.