Jira Status Sync
How Risotto ticket statuses map to your Jira workflow, what your workflow must provide, and how to troubleshoot transitions
When a department syncs tickets to Jira, Risotto keeps the Risotto ticket's status and the Jira issue's status in step — in both directions. The link between the two is the Status Mapping section of the department's ticket-sync settings.
This page explains what each mapping does, how Risotto moves issues through your workflow, what your Jira workflow must provide for transitions to succeed, and how to diagnose sync problems. For installing the integration, see Jira; for what each Risotto status means, see Ticket Statuses & Lifecycle.
What Status Mapping configures
Go to Settings. Under Departments, click a department, then click Ticket Sync. On the Jira Settings row, open the Connected menu and choose Configure.... In the Configure Jira for <department> dialog, after you choose a Jira project, the Status Mapping section lists seven Risotto statuses, Resolved, Closed, Waiting for support, Waiting for response, Waiting for approval, Paused, and Duplicate: each with a dropdown of statuses from your mapped project.
Each row answers one question: when a Risotto ticket enters this status, which Jira status should the issue move to? The same table is read in reverse for changes made in Jira.
Every row is optional — map only the statuses you want to sync.
Each row shows the Risotto status on the left and a dropdown on the right, listing the statuses from the selected Jira project. Pick a status (for example, Resolved → Done) and click Save. Not mapped is the first item in each dropdown. A row with no status shows Not mapped. To stop syncing a status that you mapped before, choose Not mapped and click Save. The department's Ticket Sync card then lists your mappings alongside the site, project, and issue type.
How Risotto moves your Jira issue
| When a Risotto ticket… | The Jira issue is transitioned to… |
|---|---|
| becomes Resolved | your Resolved mapping |
| is canceled by the requestor | your Closed mapping, or your Resolved mapping if Closed is not mapped |
| is set to Closed by an admin | your Closed mapping |
| becomes Awaiting response | your Waiting for response mapping |
| becomes Awaiting support — including escalations and reopened tickets | your Waiting for support mapping |
| becomes Awaiting approval | your Waiting for approval mapping, falling back to Waiting for support |
| is set to In progress | your Waiting for support mapping — there is no dedicated row |
| becomes Paused | your Paused mapping |
| is marked Duplicate | your Duplicate mapping |
| becomes Open | nothing — Open never syncs outbound |
| is transferred to another department | the old department's issue moves to your Closed mapping |
One rule governs the whole table: an unmapped row never syncs that status. If a row has no Jira status selected, Risotto skips the transition, with no error, no notification, and no movement. This is by design, so you can sync only the statuses that matter to your team. Two rows have extra effects when they are not mapped:
- Waiting for approval: Risotto moves the issue to your Waiting for support mapping instead.
- Resolved: Risotto never moves the issue to a done status when a ticket is resolved. A canceled ticket uses your Closed mapping; if Closed is not mapped either, Risotto does not move the issue. A move to a done status in Jira also does not resolve the Risotto ticket.
How Risotto executes a transition
Risotto never forces a status onto your issue. To move an issue to a mapped status, it:
- reads the issue's current status,
- looks up your workflow's transitions (from the copy it loaded when the integration was installed or last refreshed),
- finds a path of transitions from the current status to the target — hopping through intermediate statuses when your workflow has no direct transition, and
- executes each hop through Jira's normal transition mechanism, exactly as a user would.
If a hop turns out to be unavailable to the Risotto app user, Risotto tries an alternative route. If no route reaches the target, the sync fails and your org admins receive a Jira Sync Error notification (see Troubleshooting). Risotto can never make a move your workflow doesn't allow — every hop is subject to your permissions, transition conditions, screens, and validators.
How Jira moves your Risotto ticket
Inbound, Jira is authoritative: when someone moves the issue, Risotto follows.
- Moving the issue to a mapped status moves the Risotto ticket to the corresponding status, and Risotto notes the change on the ticket thread ("Transitioned from … to …").
- Moving the issue to an unmapped status changes nothing in Risotto.
- Moving a finished ticket's issue to your Waiting for support status reopens the Risotto ticket — this is the deliberate reopen path. The Waiting for response mapping never reopens a finished ticket.
- There are no inbound rows for Open or In progress — no Jira status change can set those.
- Risotto recognizes echoes of its own transitions and ignores them, so the two systems never ping-pong — including when two Risotto statuses share the same Jira status.
What your Jira workflow must provide
For the sync to work end to end, check your Jira project against this list:
- Every mapped status belongs to the mapped issue type's workflow. If a mapped status isn't part of that workflow, Risotto can't transition issues to it.
- A transition path exists from any status to each mapped status. Risotto may need to move an issue from anywhere in your workflow — including backwards, when a finished ticket reopens. Global transitions (allowed from "All statuses") make this automatic; one-way workflows where done statuses have no outgoing transitions break reopening.
- The Risotto app user can execute the transitions. Risotto transitions issues as its app user, so it is subject to your permission scheme and any conditions on the transitions.
- Transitions don't require input Risotto can't give. A transition screen with required fields, or a validator that rejects the request, blocks the sync.
- Refresh Risotto's copy of your workflow after editing it. Risotto caches your project's workflow and never refreshes it automatically. After changing statuses, transitions, or which workflow an issue type uses, open the department's Configure Jira for <department> dialog and click the Refresh Jira metadata button (the refresh icon next to Jira Site). The refresh clears every field in the dialog: when the metadata has loaded, click Cancel, choose Configure... again, and re-check your Status Mapping rows.
Troubleshooting
The Jira issue never changes when Risotto updates a ticket
- Check that the status is mapped: unmapped rows in Status Mapping never sync — this is by design, not an error
- Remember that some statuses never sync outbound: Open has no mapping, and a canceled ticket moves the issue to your Closed mapping, and to your Resolved mapping only when Closed is not mapped
- Confirm the mapped status still exists in the issue type's workflow
- If you recently edited your Jira workflow, click Refresh Jira metadata in the department's Configure Jira for <department> dialog
I received a 'Jira Sync Error' notification
The notification means Jira refused a transition Risotto attempted. Risotto asks Jira why and distinguishes three causes in the notification:
- The transition isn't offered to the Risotto app user — a workflow condition or a missing project permission is hiding it. Review the transition's conditions and the Risotto app user's permissions.
- The transition screen has required fields Risotto doesn't set — the notification names the fields. Make them optional, give them defaults, or remove them from the transition screen.
- The transition is available and has no required fields — a workflow validator is the likely cause. Review the transition's validators.
The Risotto ticket doesn't update when I move the Jira issue
- The destination status probably isn't mapped: only statuses selected in Status Mapping drive the Risotto ticket — anything else is ignored
- There are no inbound mappings to Open or In progress, so no Jira move can set those
- If the ticket's current status already maps to the destination Jira status (for example, two rows share one Jira status), Risotto treats the move as already in sync and does nothing
A resolved ticket reopened unexpectedly
- Moving a finished ticket's Jira issue to your Waiting for support status reopens the Risotto ticket — that's the deliberate reopen path
- Check the issue's history for who made the move — this includes Jira automation rules, since Risotto only ignores changes made by its own app user
- Tagging @Risotto in the ticket thread also reopens finished tickets
- For a ticket that came in by email, a reply by email from the requestor reopens a Resolved ticket
I edited my Jira workflow and sync stopped working
- Risotto is still using your old workflow: it caches the workflow when the integration is installed and never refreshes it automatically
- Go to Settings > <department> > Ticket Sync, open the Connected menu on the Jira Settings row, choose Configure..., and click Refresh Jira metadata
- The refresh clears the dialog's fields. When the metadata has loaded, click Cancel and choose Configure... again: the dialog shows your saved settings
- Re-check the Status Mapping rows — statuses you removed or renamed may need remapping
Something wrong or missing? Report an issue · View as Markdown