How to Change a Workflow in Jira: 6 Clear Steps for Teams
Need to change workflow in Jira without disrupting your team? Follow six clear steps to update, test, and publish changes safely. Read now to get started.
You can change a Jira workflow by editing or copying it, updating its statuses and transitions, testing the changes, and publishing them through the relevant workflow scheme. The exact steps depend on whether your project is company-managed or team-managed.
A small change can affect more than one team or work item type. If you add a status without a clear path into or out of it, issues may get stuck. If you alter a shared workflow without checking its scheme, other projects may change too.
But here's the truth: careful preparation makes workflow changes manageable. Follow these six steps to check the impact, make the edits safely, and confirm the new process works before your team relies on it.
How to Change a Workflow in Jira: 6 Steps
For a company-managed project, Jira administrators typically manage workflows under Jira settings. Team-managed projects usually let project administrators make workflow changes within the project. Start by confirming your project type and permissions.
-

1. Review the current workflow and project type
Open an issue that uses the workflow you want to change. Review its current status, available transitions, and issue type. This helps you understand how an issue moves through the process today.
Check whether your project is company-managed or team-managed. The settings and publishing process differ, so this check helps you follow the right route. If you cannot access workflow settings, ask a Jira administrator to review your permissions.
-
2. Check which projects and issue types use it
In a company-managed project, workflows are often connected to projects and issue types through a workflow scheme. Check that scheme before editing or replacing a workflow. A shared workflow may affect more teams than you expect.
For example, a workflow used by both engineering and support could contain a status that only makes sense for engineering. Identify the projects and issue types affected, then decide whether to adjust the shared workflow or create a separate one.
-
3. Edit the workflow or make a copy
In Jira settings, find the workflow you need to change. If it is active, Jira may require you to edit a draft or copy the workflow before making changes. A separate copy is useful when you want to keep the existing process available for other teams.
For a team-managed project, open the project settings and locate its workflow controls. The labels can vary by Jira version. Keep the original workflow intact until you have tested the revised one and confirmed its project assignment.
-
4. Update statuses, transitions, and rules
Add, rename, or remove statuses to reflect actual work stages, such as “Ready for review” or “Waiting for approval.” Then connect them with transitions that show how an issue can move between stages.
Review transition rules as well. Conditions control who can move an issue, validators check required details, and post functions can trigger actions after a transition. For example, an approval transition might require a reviewer before an issue can move to “Approved.”
-
5. Test the workflow with realistic issues
Try the workflow with several issue types and common situations. Check the usual route, an urgent issue, a blocked task, and a case that needs to move backward for rework. Confirm that the right people see the right transitions.
Ask a teammate who handles the work every day to test it too. They may spot a missing transition or confusing status name that an administrator overlooks. Fix issues before assigning the workflow broadly.
-
6. Publish the changes and confirm the assignment
Review Jira’s change or migration prompts before publishing. If the workflow scheme needs updating, confirm which projects and issue types will use the revised workflow. Follow the prompts carefully, especially when statuses need to be mapped.
After publishing, open a few real issues and confirm they display the expected statuses and transitions. Tell affected teammates what changed, when it takes effect, and where to report problems.
Check the Impact Before Editing
Before changing a shared workflow, find out who depends on it. In company-managed projects, the workflow scheme shows how workflows connect to projects and issue types. A change to a shared workflow can affect every area using that setup.
For example, imagine one workflow serves both bug reports and feature requests. Adding a “Needs customer response” status may help support, but confuse the product team. Separate workflows can preserve the useful parts without forcing both groups into the same path.
Here's why: a workflow is more than a status diagram. It can include permissions, validation rules, automation, and reporting assumptions. Check related project configurations and team practices before deciding how broad the change should be.
Design Statuses and Transitions Around Real Work
Use status names that describe the current state of an issue, such as “In progress,” “Ready for testing,” or “Waiting for approval.” Keep the list focused. If two statuses lead to the same action and ownership, they may create unnecessary overhead.
Transitions should make the next action clear. A reviewer should be able to move a task from “Ready for review” to “In progress” when changes are needed. A one-way path may fail when work needs to return for updates.
The best part? A clear workflow can make bottlenecks easier to spot. If many issues sit in “Waiting for approval,” the team can investigate approval delays instead of guessing where work is slowing down.
Test and Roll Out Changes Carefully
Test more than the happy path. Check whether people can reopen a completed issue, send rejected work back for revisions, and move a blocked task forward once its dependency clears. These cases reveal gaps that a simple status review might miss.
For a company-wide change, try the revised workflow with a limited project or issue type first. Compare the expected transitions with what users can actually select. For a small team-managed project, ask teammates to test the change before normal work depends on it.
Let me explain: publishing is not the end of the change. Check the workflow after rollout, listen for confusing labels, and review whether issues are getting stuck. A short follow-up can catch problems before they become the team’s new routine.
Choose a Workflow That Fits Your Team
A workflow should match the way your team handles work, not reproduce every exception as a new status. Start with the main stages and add rules only when they solve a real problem. For example, use a validator when a required approval field must be completed before an issue advances.
If several teams share a process, agree on shared terms and ownership before making changes. A product team might use “Ready for release,” while another team considers the same stage “Approved.” Clarifying those differences can prevent status confusion and reporting mismatches.
You might be wondering: should every team have its own workflow? Not necessarily. Shared workflows are easier to maintain when the process is genuinely shared. Separate workflows make sense when teams need different stages, rules, or decision points.
Jira Workflow Management with ONES.com
ONES.com is a unified platform for project management and knowledge management. ONES Project is its project management product and a Jira alternative, while ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.

For teams reviewing how they manage Jira workflow changes, ONES Project offers Jira-compatible workflows and built-in reporting. It also supports custom workflows and fields, sprint management, and automation. The platform is available as Cloud, On-Premise, Private Cloud, or Air-gapped deployments, with feature parity between cloud and self-hosted versions.
Core capabilities
- Workflows that are hard to adapt: Configure custom workflows → align project stages with how your team works.
- Different teams need different issue details: Create custom fields → capture relevant information without adding unrelated steps.
- Sprint planning needs a consistent routine: Use sprint management → organize planned work and review progress in one project environment.
- Progress is difficult to assess: Use built-in reporting → give teams and project leads clearer views of work status.
- Repeated actions take time: Set up automation → reduce manual handling of routine project steps.
- Teams rely on too many add-ons: Use native project management capabilities → reduce dependence on plugins for supported needs.
- Jira-compatible processes matter: Use Jira-compatible workflows → make it easier to evaluate a Jira alternative without assuming every team must redesign its process.
- Hosting restrictions affect adoption: Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment → fit the platform to your environment.
Application scenarios
A software team refining its delivery process: A team can configure statuses for development, review, testing, and release, then use sprint management and reporting to follow planned work. Custom fields can capture details needed for specific issue types.
An organization with restricted network requirements: A team that cannot use a cloud deployment can assess the On-Premise, Private Cloud, or Air-gapped options. Feature parity across cloud and self-hosted versions helps teams evaluate deployment needs without treating hosting choice as a feature trade-off.
ONES.com may be worth considering when your team wants project management capabilities and deployment flexibility in one platform. Evaluate its workflow fit, hosting requirements, and team needs before deciding whether it suits your environment.
Common Challenges When Changing Jira Workflows
- A change affects another team. This often happens when projects share a workflow. Check the workflow scheme and affected issue types first. If teams need different processes, consider separate workflows.
- Issues get stuck after a status change. A status may lack an incoming or outgoing transition. Test common routes and exception cases before publishing, including rework and reopening.
- Users cannot see an expected transition. Conditions or permissions may restrict who can use it. Review the transition rules and test with accounts that have different roles.
- Reports no longer match team expectations. Renamed or added statuses can affect how people interpret reports. Explain the change and confirm that reporting still reflects the stages the team needs to track.
FAQs About Changing Jira Workflows
Can I edit an active Jira workflow?
Jira may not let you directly edit a workflow while it is active. In many cases, you create or edit a draft, then publish the changes. You may also copy the workflow and update the scheme to use the copy. The exact controls depend on your project type and Jira setup, so check whether your project is company-managed or team-managed before starting.
Will changing a workflow affect existing issues?
It can. A workflow change may alter which statuses or transitions are available to issues using that workflow. When you update a workflow scheme, Jira may ask you to map existing statuses to statuses in the new setup. Review those prompts and test affected issue types so existing work remains easy to track.
Can I add a new status without changing the whole workflow?
Often, yes. You can add a status and connect it with the transitions that make sense for your process. Check the workflow scheme and any rules tied to the current workflow first. A new status that has no usable transition can leave issues stranded, so test how an issue enters and exits it before publishing.
What is the difference between company-managed and team-managed workflows?
Company-managed projects typically use workflows configured by Jira administrators and connected through workflow schemes. Team-managed projects usually provide project-level controls that project administrators can manage within that project. This distinction affects where you make changes and how broadly they apply. Confirm your project type first, then use its settings to make and test the update.
Conclusion
Changing a Jira workflow is safest when you understand the project type, check who shares the workflow, and test the revised process before rollout. Review statuses, transitions, rules, and scheme assignments so the change supports real work rather than creating new roadblocks.
But here's the truth: even a well-planned change needs follow-up. Confirm the workflow works with real issues, tell teammates what changed, and adjust anything that causes confusion. With those steps, your team can make workflow changes with fewer surprises and a clearer path through its work.