Skip to content

Migrating from Jira Service Management approvals to DueReason

A JSM approval step blocks a request's workflow status until someone clicks Approve. See what's missing and what changes moving it to DueReason.

Updated · 9 min read

In short

  • Jira Service Management lets you add an approval step to any status in any request type's workflow - access requests, purchases, leave, IT changes - and the people who approve it don't even need a JSM license, only to be a customer of the service project.
  • What the step produces is a request sitting in an "approved" status inside Jira: not a signed, independently verifiable object the next system checks before it acts, the same gap the Kissflow and Power Automate migration guides describe for a process step or a flow action.
  • DueReason doesn't replace JSM's request portal, queues or workflow engine - it answers the one approval question a status-gated step asks, for the request types where that answer needs to travel with a signed, verifiable record instead of staying inside Jira.
  • Moving one approval step doesn't mean moving the request type: keep JSM for the portal, SLAs and queue your agents work from, and add DueReason for the one status that needs a decision another system can check on its own.

If your IT or Ops team gates a request behind an approval step inside a Jira Service Management workflow - a new-account request, an access change, a purchase over a threshold - this walks through what that step does today, and what changes if you move just that one step to DueReason.

What a JSM approval step does today

A JSM admin can add an approval step to any status in any request type's workflow: select the status in the workflow diagram, turn on Include approval step, and configure how many approvers are needed and where they come from - a user picker or group picker custom field, optionally including whoever is responsible for an affected service. Once a request reaches that status, the assigned approvers are notified by email and can approve or decline from the help center, straight from the email, or from Slack or Microsoft Teams if chat is connected; the request then transitions to whichever next status the workflow defines for an approval or a decline. Setting this up needs a Jira administrator and only works in company-managed service projects, not team-managed ones.

Approvals are not a separately purchased product bolted onto Jira Service Management - they are a property of the workflow attached to a request type you already pay for, which is also why Atlassian's own documentation is explicit that an approver "doesn't need a Jira Service Management license to approve requests," only to be a customer of the service project the request belongs to. That is a deliberate design choice for ITSM requests, where the person signing off on an access change or a purchase is frequently a manager or a budget owner outside the team running the service desk, not a licensed agent.

What happens after a request transitions

Jira's own documentation describes the request moving to the next status in the workflow once approved, and the requester being notified of any comments the approver left - it does not describe a signed or otherwise independently verifiable object the next step, integration or person checks before acting. The trust sits in the request now being in whatever status the workflow calls "approved," the same gap the Kissflow migration guide describes for a process instance marked approved inside its own engine, and the Power Automate migration guide describes for a flow that simply resumes once someone responds to the approval card. Whatever runs next - an automation rule, a script polling the Jira REST API, a person reading the status column in a queue - is trusted to have been wired to the right status by whoever built the workflow, not verifying anything about the decision itself.

The same shape in DueReason

JSM's request types are general-purpose IT service management, so no single DueReason template is a 1:1 replacement for a whole request type - DueReason answers the approval question the status-gated step asks, not the queueing, SLAs or portal around it. Map the step, not the request type: for access requests, account changes or offboarding (access request approval, offboarding checklist approval), Account or access actions from Settings → Templates models the same restrict/suspend/revoke decision with its own reviewer and legal groups; for a change request gating a release, Production deployments fits the same shape IT change management asks for. For a step with no close template match - a purchase request, an exception to policy - a custom DueReason action models the same approve/reject question with its own approver group and its own evidence field in place of the step's custom-field attachment.

Whichever action models the step, once a request is decided DueReason issues a signed, single-use grant bound to the exact payload - who the access change affects, what is being revoked, which environment a deployment targets - which whatever acts next verifies, rather than trusting that the request sits in the right status inside Jira.

What changes, not just what moves

  • A grant the acting system checks, not a status read back from a queue. DueReason's signed grant is bound to a hash of the exact payload and verified by whatever executes the decision, so a changed target or scope after approval is refused rather than carried out because the request happened to be in an approved status.
  • A hash-chained ledger, not a request's own activity log. Every step of a request - filed, each answer, what happened after - is a ledger event from the start, checkable on its own without opening the Jira project that hosted the approval step.
  • Evidence built into the action, not a generic custom field. JSM's approval step attaches whatever a request type's form already collects; DueReason's evidence setting (none, text or document) is narrower by design - built into the action definition itself, so the decision record always carries exactly what the approver was shown, independent of whatever else the request's form happened to capture.
  • An agent-native surface, not a status that only advances through the portal or the REST API. The same actions are reachable from @duereason/sdk, the MCP server, the GitHub Action or the REST API, so a pipeline or an agent can requestApproval() and waitForApproval() directly, without a Jira request or a workflow transition involved at all.

Moving one approval step over

  1. Pick the one approval step you want to move - not the whole request type - and find the closest DueReason template (Account or access actions, Production deployments) or define a custom action if nothing close exists yet.
  2. Recreate the people who currently approve that step as members of the action's approver group, in place of the custom field's user or group picker in Jira.
  3. For requests still filed by a person through the help center, the console request form replaces reaching the approval status: pick the action, attach what the request type's form used to collect, write a reason.
  4. For requests your automation rules or integrations create automatically, requestApproval() and waitForApproval() from @duereason/sdk (or the no-code webhook recipe if you would rather not write a backend) replace the point where the request reached the approval status.
  5. Replace whatever reads the request's approved status back into an automation rule or a downstream system with a check of decided.status and a verification of decided.grant before the step that actually acts - the system doing the work should check the grant, not just the status column.

What has no direct equivalent

DueReason has no request portal, no queues, no SLAs, and no incident, problem or change management of its own - it is not an ITSM replacement and does not try to be. If the real value you get from Jira Service Management is the rest of the service desk - the portal your requesters use, the queues your agents work from, the SLAs you report on - keep JSM for that and add DueReason around the one status that needs a signed, independently verifiable decision rather than expecting a native replacement for the service management platform itself.

Questions

Does moving to DueReason mean giving up our Jira Service Management portal and queues?
No. DueReason replaces one approval step at a time, not the request type or the service desk around it. Keep JSM for the portal, queues and SLAs, and point the one status that needs a signed, verifiable decision at a DueReason action instead.
Does JSM's approval step really have no verification step of its own?
Atlassian's own documentation describes the request moving to the next workflow status once approved, with the requester notified of any comments - it does not describe a signed or independently verifiable decision object the next step checks before it acts. Whoever built the automation rule or the integration after that status is trusted to have wired the right thing.
Do approvers need a Jira Service Management license?
No - Atlassian's documentation is explicit that approvers only need to be customers of the service project, not licensed agents. DueReason's approver groups work the same way: anyone you add can approve from the console or a connected notification channel without a seat in the system of record the request came from.
What does Jira Service Management cost, compared to DueReason?
Jira Service Management's published annual pricing lists Standard at around $20 per agent per month and Premium at around $51 per agent per month, with Enterprise on a custom quote; approvals ship as part of the workflow you already configure, not a separate purchase. DueReason is free today for one organization with up to five members, all core features included.
Do I need engineering to move one approval step over?
No. Picking the closest template, adding people to its approver group, and filing requests from the console form is console-only setup, the same as reaching an approval status by hand in Jira; engineering is only needed once you want an automation rule or an agent to request approval through the API instead of a person using the help center.

Move one approval step to DueReason

Keep Jira Service Management for the portal, queues and SLAs around it - point requestApproval() and waitForApproval(), or the console request form, at the one status that needs a signed, verifiable decision.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates