A Jira workflow is the set of statuses a work item moves through, plus the transitions that move it from one status to the next. As of October 2026 every transition is one-way, so letting a work item go back and forth between two statuses needs two separate transitions.
Here's the catch. Once a workflow is active it's partly locked: you can't rename it, and if it sits in a workflow scheme shared by several spaces, one change hits every one of those spaces. Built-in workflows can't be edited at all; you copy them and edit the copy.
Statuses and transitions
A status is where a work item is right now, such as To Do or In Progress. A transition is the move between two statuses. The one-way rule is the bit that confuses people when they first open the editor. If you add a transition from In Progress to In Review, there's no way back to In Progress until you add a second transition going the other way.
A transition can also loop back to the same status. That sounds odd, but it's useful: you can use it to open a screen or fire an action without moving the work item anywhere.
The default statuses you'll see
Default statuses depend on the template you picked. Common ones include To Do, In Progress, Done and In Review. Jira also has its own set: Reopened, Resolved, Closed, Backlog and Selected for Development. The recruitment, lead-tracking and procurement templates add their own, such as Screening, Lost, Won and Purchased.
So if two spaces in the same company show different status names, that's normally the template, not a mistake.
Who can edit a Jira workflow
| Space type | Who can edit workflows |
|---|---|
| Company-managed | Site admins, and users with the edit workflows permission |
| Team-managed | Site admins and space admins |
That split matters when someone asks you to add a status and you can't find the option. In a company-managed space, being a space admin on its own isn't the same as holding the edit workflows permission.
Active and inactive workflows
An inactive workflow is one no space is using, and you can edit it freely. An active workflow can still be edited, but your changes only go live when you publish them with Update workflow, and you can discard them instead if you change your mind. What you can't do is change an active workflow's name. To get a new name, copy the workflow and use the copy.
Workflow schemes and why they matter
A workflow scheme maps workflows to work types, so bugs can follow one workflow and tasks another. One scheme can be shared by many spaces, which is efficient until you edit it, because a change to a shared scheme affects every space using it.
Default schemes can't be configured, only copied. Editing an active scheme creates a draft, and nothing changes for anyone until you publish that draft. And an active scheme can't be deleted until it's been disassociated from every space.
Jira workflow rules at a glance
| Item | Rule |
|---|---|
| Transition | One-way; two are needed to go back and forth |
| Built-in workflow | Can't be edited; copy it instead |
| Active workflow name | Can't be changed; copy and activate the copy |
| Active scheme | Edits make a draft; publish to apply |
| Shared scheme | A change affects every space using it |
| Active scheme deletion | Only after it's disassociated from all spaces |
How to build a Jira workflow
- Go to Settings, then Work items, then Workflows.
- Copy a built-in workflow, or start a fresh one.
- Add your statuses and transitions in the editor, remembering each transition only goes one way.
- Publish with Update workflow.
- Add the workflow to a workflow scheme and associate that scheme with a space.
If the scheme is shared, check which other spaces use it before you publish. That one look saves a lot of confused messages from teams who suddenly find a new status on their board.
Here's what the one-way rule means in practice. A simple flow of To Do, In Progress, In Review and Done has four statuses but needs at least four transitions: three going forward, and one from In Review back to In Progress for work that needs changes. Add a route from Done back to In Progress for reopened work and you're at five. Sketch the arrows on paper before you open the editor.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Ask Rovo to explain a workflow
If you've inherited a workflow and can't work out why work items move the way they do, Rovo can talk you through it. Type /explain-workflow in Rovo Chat, or choose Explain workflow from the status dropdown. Rovo can see validation rules and their parameters, but not the parameters of condition rules, so a transition that's hidden by a condition may still need a look in the editor.
There's more on this in Jira Backlog.
My verdict on Jira workflows
I'd keep workflows short and copy before you change anything shared. Most teams need a handful of statuses and transitions in both directions, and every extra one is a choice your team has to make on every work item. If you're comparing Jira with other tools because the setup feels heavy, my ClickUp and Jira comparison is worth a read, and service teams should see how ServiceNow stacks up against Jira Service Management.
A clean workflow keeps a team moving. Getting that team working well with AI is where I come in. I run AI training and workshops for teams, and help businesses with AI enablement, AI automation and GEO, which is about getting your business seen and cited in AI answers. Most of that work is with SaaS marketing teams, telecom companies and small businesses. Here's how we can work together.
Frequently asked questions
What is the difference between a status and a transition in Jira?
A status is where a work item is. A transition is the one-way move between two statuses, so going back and forth needs two transitions.
Can I edit a built-in Jira workflow?
No. Built-in workflows can't be edited, but you can copy one and use the copy as a base.
Can I rename an active Jira workflow?
No. An active workflow's name can't be changed. Copy the workflow instead.
Who can edit workflows in Jira?
In company-managed spaces, site admins and users with the edit workflows permission. In team-managed spaces, site admins and space admins.
Why can't I delete a Jira workflow scheme?
An active workflow scheme can't be deleted until it's disassociated from all spaces.
