Changing a Jira Workflow: Where You Edit It, and What It Does to Open Work
You need one more status between In Progress and Done, or a rule that stops anyone closing a bug without a fix version. Where you make that change depends on the kind of space you're in, and in a company-managed space one edit can reach every other space sharing the same workflow. Jira now calls issues work items and projects spaces, so the menus may not match older guides.
Team-managed and company-managed spaces edit workflows differently
One workflow per work type, owned by the space
- Open Space settings, then Work types, pick the type and choose Edit workflow.
- Edits stay inside that space. There are no workflow schemes to manage.
- Rules are a short list: assign the work item, restrict who can move it, check a field, check whether it has been through a status, and update a field.
- You need the Administrator role in that space.
Shared workflows, applied by a scheme
- A workflow scheme decides which workflow each work type in the space follows.
- One workflow can serve many spaces, so an edit lands in all of them. The editor lists the spaces it affects before you publish.
- Transitions take the full rule set: conditions, screens, validators and post functions.
- Editing a shared workflow is normally a Jira admin's job.
In a team-managed space and need a validator it doesn't offer? That's usually the point to move the team to a company-managed space, or to enforce the check with an automation rule instead.
Adding a status and a guarded transition in the workflow editor
This follows a company-managed workflow in the current editor. The legacy editor used older names for the same rules, mapped below.
- 1
Open the workflow your work type really uses
Space settings › WorkflowsEdit the workflow attached to the work type you're changing. Before touching anything, read the panel that lists which spaces use it.
- 2
Add the status
Add it from the toolbar and drag it into place on the diagram. A status with no transition leading into it can't be reached, so draw one straight away. If you'd rather work from a list, switch the editor to text mode.
- 3
Draw the transition and give it rules
Select the transition and open its rules. The editor groups them as Restrict transition (who can make the move, formerly conditions), Request input (a screen to fill in), Validate details (formerly validators, such as a required field) and Perform actions (formerly post functions, such as setting the assignee).
Watch for: when a validation fails, the move is blocked and the actions don't run. Test it on a real work item, not just the diagram.
- 4
Remove what you no longer need
Deleting a status that still holds work items walks you through moving them to another status. Decide where they belong before you start, rather than in the dialog.
- 5
Publish
Choose Update workflow and the change is live at once in every space listed. Discarding instead puts the workflow back the way it was.
Before you choose Update workflow
Which spaces share this workflow?
A tweak meant for one team's bug flow also changes it for every space on the same scheme. If only one space should change, copy the workflow and assign the copy to that space's scheme.
Is a board column built on the status you are removing?
Board columns are mapped from statuses. Look at the board's column settings after the change so moved work items show up where the team expects them.
Do any automation rules or saved filters name that status?
A rule that fires on "transitioned to QA", or a filter on
status = QA, stops matching anything once QA is gone. Search your automation rules and JQL filters first.Who is allowed to make each move?
A restriction tied to a role or group that later changes can leave nobody able to close work. Atlassian warns about exactly this for team-managed rules.
What should happen outside Jira when the move happens?
Billing, a support queue, a client page. Settle it now, while the transition is being drawn, not after the team has learned the new flow.
When a status change has to count outside Jira
Rules on a transition can do plenty inside Jira: reassign the work item, set a field, add a comment. Getting the same move to update an invoice, notify a support team in another tool or change what a client sees means leaving Jira's own rule set, through an automation rule that sends a web request, a webhook to a service you run, or an app.
The cheapest time to plan that is during a workflow redesign. Bolting it on later usually means guessing which status meant what, and rebuilding rules that already depended on the old names. n-frames builds the outside half at the same time as the new workflow, so each status means the same thing everywhere it shows up. Systems with no ready-made app are covered on the Jira integrations page.
Questions people ask
How do I edit a workflow in Jira?
In a team-managed space, go to Space settings, then Work types, choose the type and select Edit workflow. In a company-managed space, open the workflow from the space's Workflows settings, or from the admin workflow list. Add statuses and transitions on the diagram, attach rules to transitions, then choose Update workflow to publish.
Can I create a custom workflow in Jira?
Yes. Build one from scratch or copy an existing workflow and change it. In company-managed spaces you then assign it to work types through a workflow scheme. In team-managed spaces each work type simply gets its own workflow.
What is a workflow scheme in Jira?
In company-managed spaces, a workflow scheme maps each work type to a workflow, so bugs, stories and tasks can follow different paths. Several spaces can share one scheme, which is why one edit can affect them all. Team-managed spaces don't use schemes.
What are workflow transitions?
The allowed moves between statuses, drawn as arrows on the diagram. Each one can carry rules: who may make the move, a screen to fill in, checks that must pass first, and actions that run once the move is made.
Will changing a Jira workflow affect work items already in progress?
It can. Updates go live straight away in every space using that workflow, and deleting a status makes you move its work items somewhere else. Adding a status or a transition is low risk. Removing or renaming ones that boards, filters or rules depend on is where care pays off.
Who builds what a Jira transition should set off in other systems?
n-frames builds and hosts it: a listener for the transitions you care about that updates billing, support or client-facing pages, retries when the other system is down, and tells you when something didn't go through.