Edit a Jira Workflow: A Step-by-Step Guide for Jira Teams
Need to edit jira workflow without disrupting work? Follow this step-by-step guide to update and test changes safely. Read now to learn how.
Editing a Jira workflow can look like a small settings change, until a status disappears or a ticket gets stuck. A new transition may affect several projects, and changing an active workflow can disrupt work already in progress.
It’s easy to focus on the status names and miss the rules that control who can move an issue, when they can do it, and what happens afterward. That can leave your team with confusing options or blocked work.
But here's the truth: you can make a workflow change safely when you check its scope, edit the right configuration, and test the result before publishing. Here’s a practical Jira workflow editing guide, from finding the workflow to verifying its transitions with your team.
How to edit a Jira workflow safely
Start by identifying the project and workflow you need to change. Then edit a draft when Jira offers one, test your changes, and publish only after checking who and what they affect.
Confirm the project type and your permissions. Open the project settings and check whether the project is company-managed or team-managed. You may need Jira administrator or project administrator permissions to make the change.
Find the workflow attached to the project. In a company-managed project, check the project’s workflow settings or the workflow scheme associated with it. In a team-managed project, workflows are generally managed within that project’s settings.
Check where else the workflow is used. A company-managed workflow may be linked to more than one project or issue type through a workflow scheme. Confirm the scope before changing it so you don’t unintentionally alter another team’s process.
Open the workflow editor. Locate the workflow and choose its edit option. Jira’s interface can differ by project type and product version, so use the project’s settings and current workflow configuration as your guide.
Make the smallest useful change. Add or rename a status, adjust a transition, or update its rules. For example, you might add a “Ready for Review” status between “In Progress” and “Done.”
Review transition rules. Check conditions, validators, and post-functions. A condition controls whether a transition is available, a validator checks information before the move, and a post-function performs an action after it.
Test the draft or change. Walk through the workflow as a teammate would. Check whether the expected transitions appear and whether restrictions or required fields behave correctly.
Publish and verify. If Jira presents a draft or publish step, review any warnings before applying it. Afterward, check the workflow in the project and confirm that existing issues still move as expected.
Here's why the order matters: changing a status without checking transitions can create a dead end. For instance, a ticket may reach “Ready for Review” but have no path to “Done.”

Understand what a Jira workflow controls
A Jira workflow defines the statuses an issue can occupy and the transitions that move it between them. It can also include rules that limit or validate those transitions.
Think of a workflow as a route through a team’s work. A simple software task might travel from “To Do” to “In Progress,” then “Code Review,” and finally “Done.” A transition is the permitted step between two points.
Statuses describe the current stage
Status names should help your team understand what is happening without opening every issue. If “In Progress” includes active coding and waiting for review, consider whether those stages need separate statuses.
Each additional status can improve visibility, but it can also add maintenance. For a small team, a short flow with clear definitions may be easier to follow than a long chain of narrowly defined stages.
Transitions determine what can happen next
Transitions control the movement between statuses. They may be available from one specific status or from multiple points, depending on the workflow design.
For example, a “Reopen” transition might move a completed issue back to “In Progress.” If that transition is missing, the team may need an administrator to correct an issue that has returned for more work.
Rules shape access and quality checks
Conditions, validators, and post-functions affect how transitions behave. A condition might limit a transition to a particular role, while a validator might require a resolution before an issue can close.
Let me explain: a status can appear correctly in the editor while the transition to it remains unavailable in practice. Check both the route and its rules when investigating a blocked issue.
Prepare before you change a workflow
A few minutes of preparation can prevent a workflow change from affecting more work than intended. First, describe the problem in plain language, such as “review work is invisible until the task is complete.”
Then identify the smallest change that would solve it. If the team needs to distinguish review from implementation, adding one review status may be clearer than creating several new stages.
Map the current path
Write down the statuses an issue passes through today and the transitions available at each stage. Ask a teammate to check the map against a real issue, not just an ideal example.
For a bug fix, the route might be “To Do” → “In Progress” → “Ready for QA” → “Done.” If urgent fixes can bypass testing, record how that exception should work before editing.
Check workflow scope and issue types
In company-managed projects, workflow schemes can connect workflows to issue types. A change intended for stories might also affect bugs or tasks if those issue types share the same workflow.
Confirm whether another project uses the same workflow. When a shared workflow serves different teams, a change that seems obvious for one group can add confusing steps for another.
Agree on what success looks like
Set a simple check before editing. For example, “Every issue entering Ready for QA must have a testing owner” gives you a concrete result to verify.
You might be wondering: do you need a complete redesign? Usually, the first change should address a specific bottleneck. Keep a clear reason for each status or rule you add.
Test workflow changes before publishing
Testing helps you catch a broken route while the change is still easy to correct. Use a test project or a safe draft where possible, especially when a workflow is shared across projects.
Try the workflow with different issue types and roles. A transition that works for an administrator may be hidden from a developer if its condition restricts access.
Walk through common and unusual paths
Test the normal route first. Create or select a sample issue, move it through each expected status, and check that required fields appear at the right moments.
Then test exceptions. Reopen a completed issue, try to close an issue with missing information, and check whether a team member without a special role can use restricted transitions.
Check the impact on work already in progress
Changes to active workflows can affect issues that are already using them. Review Jira’s warnings and any migration or status-mapping prompts before confirming a publication.
If Jira asks you to map statuses, match each existing status to the intended new one carefully. A careless mapping can leave open issues in an unexpected stage or make their next transition unclear.
Ask a teammate to verify the result
Have someone who performs the work test the route using their normal permissions. They can spot practical confusion that an administrator may overlook, such as two statuses that sound nearly identical.
The best part? A short test can reveal both technical and wording problems. If a teammate can’t tell whether an issue is waiting for review or actively being reviewed, revise the labels or guidance.
Publish changes and keep the workflow usable
When the workflow behaves as intended, publish the change through Jira’s available workflow controls. The exact steps depend on the project type and whether you edited a draft or an active configuration.
After publication, verify the affected project, issue types, and transitions. A quick check on a real issue can confirm that the new status appears and that the expected next step is available.
Tell the team what changed
Explain which status or transition changed and when teammates should use it. For example, “Move a task to Ready for QA when implementation is complete and testing can begin.”
Share the guidance where the team regularly checks its process. Clear instructions reduce inconsistent status use, especially when a new stage changes handoffs between developers and testers.
Review the workflow after real use
Watch for issues that repeatedly stall or take unexpected routes. If several tickets stop at “Ready for QA,” check whether the team understands the handoff or whether a transition rule is blocking progress.
Keep the workflow aligned with actual work. A quarterly review may be enough for a stable team, while a team changing its delivery process may need to check sooner.
ONES.com Solution: Manage project workflows with ONES Project

Value proposition
ONES.com is a unified project management and knowledge management platform, with ONES Project providing project management capabilities as a Jira alternative. Teams can manage work with configurable workflows and keep process guidance in ONES Wiki, which is sold separately.
ONES Project supports Jira-compatible workflows, reporting, custom fields, sprint management, and automation. Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment, with feature parity between cloud and self-hosted versions.
Core capabilities
Pain: Your team needs a process that differs from the default. ONES capability: Custom workflows and fields let you shape stages and issue details around the work. Result: Teams can track relevant handoffs without relying on unnecessary workarounds.
Pain: A workflow change leaves teammates unsure about the next step. ONES capability: ONES Project supports Jira-compatible workflows. Result: Teams familiar with Jira-style processes can work with recognizable workflow patterns.
Pain: Project leads lack a clear view of progress. ONES capability: Built-in reporting helps present project information. Result: Leads can review work status without assembling multiple separate reports.
Pain: Sprint planning and workflow tracking feel disconnected. ONES capability: Sprint management works alongside project workflows. Result: Teams can coordinate sprint tasks and status changes within one project management environment.
Pain: Repeated manual steps slow down routine work. ONES capability: Automation supports recurring project actions. Result: Teams can reduce repetitive administration and keep common steps more consistent.
Pain: Extra plugins complicate the workflow setup. ONES capability: Core project management features include workflows, custom fields, reporting, and sprint management. Result: Teams can assess whether fewer add-ons meet their day-to-day needs.
Pain: Hosting requirements limit where project work can run. ONES capability: Cloud, On-Premise, Private Cloud, and Air-gapped deployments are available. Result: Teams can select a deployment model that fits their operating environment.
Pain: A team wants to try project management before committing broadly. ONES capability: ONES.com offers a free option for up to 30 seats. Result: A team can evaluate the platform with a defined group before deciding how to proceed.
Application scenarios
A software team moving from Jira can assess ONES Project for Jira-compatible workflow needs, sprint management, custom fields, and reporting. It can test a representative project and compare how its existing handoffs work.
A team with restricted network requirements can consider an On-Premise, Private Cloud, or Air-gapped deployment. It can also use ONES Wiki, sold separately, to maintain process guidance alongside project management work.
Common challenges when editing a Jira workflow
Problem: A teammate cannot see a transition. Check its conditions and the teammate’s project permissions. If a rule limits the transition to a role, confirm the person has the intended role.
Problem: Issues get stuck in a new status. Review the available outgoing transitions and their rules. Add or correct a route that matches the next real step in the process.
Problem: A change affects another project. Check whether the workflow is shared through a workflow scheme. Where possible, separate workflows when teams need meaningfully different processes.
Problem: The new workflow is harder to understand. Remove stages that do not clarify ownership or progress. Use status names the team can distinguish during everyday work.
Problem: Existing issues appear in the wrong stage after publication. Review Jira’s status-mapping prompts and confirm the intended mapping before publishing. Then inspect a few active issues to verify their routes.
FAQs about editing Jira workflows
Who can edit a Jira workflow?
The required permission depends on the project type and workflow configuration. Company-managed projects often require Jira administrator access for workflow changes, while some team-managed settings may be controlled within the project.
If you can view project settings but cannot edit the workflow, ask a Jira administrator to check your permissions. Confirm the project type before following instructions for a different setup.
Can I edit a workflow that is already in use?
Jira may let you edit an active workflow through a draft or prompt you to publish a change. The available process depends on the workflow and project configuration.
Before publishing, review warnings, affected projects, and any status-mapping steps. Test the updated route and check active issues afterward to make sure they remain in the expected stages.
Why can’t I move an issue to the next status?
The transition may not exist, or a condition could hide it from you. A validator may also prevent the move until required information is added.
Check the issue’s current status, the workflow transition, and the rules attached to it. If the transition should be available but remains missing, ask a Jira administrator to inspect permissions and workflow configuration.
Should every work stage have its own status?
No. Add a status when it gives your team useful visibility or clarifies a handoff. For example, separating “In Progress” from “Ready for QA” can show when testing can begin.
If two statuses mean almost the same thing, teammates may use them inconsistently. Keep the route as simple as your team can use reliably, then add detail only when it solves a real tracking problem.
Conclusion
Editing a Jira workflow safely starts with a clear problem and a check of the workflow’s scope. Make a focused change, review transition rules, and test the route with the people who will use it.
If a change could affect other projects or active issues, pause to check the workflow scheme and Jira’s publication prompts. Then explain the new steps and watch for issues that stall after the change.
A workflow should make progress easier to see, not add uncertainty. With careful testing and simple status names, your Jira team can improve its process while keeping everyday work moving.