Map workflow statuses, choose a sync direction, and control subscriber emails for incoming Jira changes.
Map your feedback statuses to Jira workflow statuses so a change in one product can update the linked work in the other.
You need a connected Jira account and a linked issue. Automatic creation and manual linking both use the board’s status rules.
Choose a direction
- Open Settings → Integrations → Jira → Manage connections.
- Find the matching rule under Board rules, or add one.
- Select the feedback board, Jira project, and issue type.
- Under Status sync, choose how updates should travel.
The Status sync menu with both directions, either one-way direction, and Off
| Direction | Behavior |
|---|---|
| Both directions | A mapped change in either product updates the other. |
| Jira → Userorbit | Jira changes update feedback; feedback changes do not move the Jira issue. |
| Userorbit → Jira | Feedback changes move Jira issues; Jira changes do not update feedback. |
| Off | The rule does not synchronize statuses. Automatic creation can still be enabled. |
Map your statuses
Choose the matching Jira status beside each feedback status you want to sync. The Jira options depend on your selected project and issue type.
Our example uses:
| Userorbit | Jira |
|---|---|
| In review | To Do |
| In progress | In Progress |
| Completed | Done |
Both directions selected with In review mapped to To Do, In progress to In Progress, and Completed to Done
Leave a status as Not synced to exclude it. Each Jira status can be used once within a rule, so an incoming change has one clear destination. At least one mapping is required when status sync is enabled.
Click Save settings. A board-specific rule takes priority over All other boards.
Allow time for incoming changes
Userorbit sends mapped feedback status changes to Jira automatically. The example below shows Jira reflecting an In progress change made on the feedback.
Jira issue KAN-6 showing In Progress after the linked feedback changed in Userorbit
Incoming Jira changes are checked in the background approximately every five minutes. They are not instant. The linked feedback view can update when the next background sync completes.
The open Userorbit feedback showing In Progress after Jira’s change was picked up automatically
You can also open the feedback’s Jira dialog and choose Refresh status to check immediately.
Choose whether subscribers receive emails
Enable Notify subscribers when Jira changes the feedback status if you want incoming changes to trigger the usual eligible subscriber notifications. Leave it off when testing or when you want to suppress customer emails caused by Jira status updates.
This follows normal subscriber eligibility and delivery rules. It does not email every workspace user or disable unrelated feedback notifications.
The fallback status setting
The separate Sync feedback status from Jira checkbox applies only when no board rule matches. It maps Jira status categories as follows:
- To Do → Planned
- In Progress → In progress
- Done → Completed
Use board rules for exact status mappings, board-specific behavior, or outgoing synchronization.
What does not synchronize?
Unmapped statuses remain unchanged. Archived feedback is not updated automatically, and a Jira Done status does not automatically complete replay-observed feedback.
Status synchronization does not mirror assignees, priorities, comments, or arbitrary custom fields. Use Update from feedback to send the current feedback title and description manually. See Create, link, and import Jira issues.
If a mapped change is not appearing, see Troubleshoot Jira creation and sync.