Hi there RE the new workflow editor - see ref links and docco below I just updated some workflows to replace an old status with new one and, in some cases, I replaced duplicate statuses (Eg. Reopen and Reopened, so I just changed all to use Reopened instead) Now, my question or discussion-trigger is: * Is the old workflow editor going to be removed at some stage and if so, when? * It was a breeze to make the updates above so i could delete the old/duplicate statuses. I feel a bit weary and suspicious that this was so easy to do in the new workflow editor! * Is there any caveats or cautions that I need to be made aware of with the new workflow editor at all? Ie. i did check automation rule JSON export to see if any automation rule uses the old status ... but is there anything I need to check or make sure or know of with the new editor? https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-new-workflow-editor/ https://community.atlassian.com/forums/Jira-articles/Jira-s-New-Workflow-Editor-for-Team-Managed-Projects/ba-p/2570451 There may be more docco but I couldn't find it right now Also, thanks Atlassian, for making the new workflow editor so easy to use! Thank you Yatish

Hello @Yatish Madhav Currently, Atlassian has not announced a definitive date for the removal of the old workflow editor. Looking at my Jira instance, both the old and new workflow editors are available, and you can switch between them as needed. Atlassian is actively developing the new workflow editor and working to bring important features from the old editor into the new experience. Until feature parity is reached, you are encouraged to use whichever editor best fits your needs, and you can set your preferred default editor for convenience. You can refer to the guide here for Features in the new Workflow While the new editor is user-friendly, there are some important considerations: * Feature Gaps: Some advanced features and rules are still only available in the old editor. For example, certain conditions, validators, and post-functions-such as "User Is In Group Custom Field," "Field Required Validator," "Looped transitions," "Exporting workflows," and "Triggers"-are not yet supported in the new editor. If your workflows depend on these, you may need to switch back to the old editor to configure them. * Rule Mapping: The new editor groups rules differently (Conditions, Validators, Post-functions) and replaces many old rules with new equivalents. However, not all legacy rules have direct replacements yet. * No Workflow Rule Triggers on Status Migration: When you delete a status and reassign issues to a new status, workflow rules (such as conditions, validators, and post-functions) are not triggered during this migration. This means automated actions or restrictions tied to transitions won’t execute for these bulk status changes. https://support.atlassian.com/jira-software-cloud/docs/move-issues-to-new-statuses-while-updating-your-workflow/ * Project Impact Visibility: The new editor allows you to see which projects use the workflow before publishing changes, helping you avoid unintended impacts. * Testing Recommended: As with any significant workflow changes, it’s best practice to test updates in a staging or small project before rolling out changes broadly. https://community.atlassian.com/forums/App-Central-articles/Best-Practices-for-Managing-Workflow-in-Jira/ba-p/2944228 What to check after Status Updates * Automation Rules: You’ve already checked automation rule JSON exports for references to old statuses, which is excellent. Continue to ensure no automations, filters, or reports reference deprecated statuses. * Status Mappings: Double-check that all issues previously in old or duplicate statuses have been correctly migrated to the new status. Use Jira’s search/filter tools to confirm no issues are left in now-obsolete statuses. * Workflow Rules and Permissions: Review any custom workflow rules and permissions, especially if you previously used advanced conditions or validators that may not yet be available in the new editor. * Integrations: If you have external integrations (e.g., with GitHub, Slack, etc.), verify that they are not referencing old statuses.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New Workflow Editor

Yatish Madhav

Hi there

RE the new workflow editor - see ref links and docco below

I just updated some workflows to replace an old status with new one and, in some cases, I replaced duplicate statuses (Eg. Reopen and Reopened, so I just changed all to use Reopened instead)

Now, my question or discussion-trigger is:

Is the old workflow editor going to be removed at some stage and if so, when?
It was a breeze to make the updates above so i could delete the old/duplicate statuses. I feel a bit weary and suspicious that this was so easy to do in the new workflow editor!
Is there any caveats or cautions that I need to be made aware of with the new workflow editor at all? Ie. i did check automation rule JSON export to see if any automation rule uses the old status ... but is there anything I need to check or make sure or know of with the new editor?

https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-new-workflow-editor/

https://community.atlassian.com/forums/Jira-articles/Jira-s-New-Workflow-Editor-for-Team-Managed-Projects/ba-p/2570451

There may be more docco but I couldn't find it right now

Also, thanks Atlassian, for making the new workflow editor so easy to use!

Thank you
Yatish

Accepted answers

Usman_ju24nf

Hello @Yatish Madhav

Currently, Atlassian has not announced a definitive date for the removal of the old workflow editor. Looking at my Jira instance, both the old and new workflow editors are available, and you can switch between them as needed. Atlassian is actively developing the new workflow editor and working to bring important features from the old editor into the new experience.

Until feature parity is reached, you are encouraged to use whichever editor best fits your needs, and you can set your preferred default editor for convenience.

You can refer to the guide here for Features in the new Workflow

While the new editor is user-friendly, there are some important considerations:

Feature Gaps: Some advanced features and rules are still only available in the old editor. For example, certain conditions, validators, and post-functions-such as "User Is In Group Custom Field," "Field Required Validator," "Looped transitions," "Exporting workflows," and "Triggers"-are not yet supported in the new editor. If your workflows depend on these, you may need to switch back to the old editor to configure them.
Rule Mapping: The new editor groups rules differently (Conditions, Validators, Post-functions) and replaces many old rules with new equivalents. However, not all legacy rules have direct replacements yet.
No Workflow Rule Triggers on Status Migration: When you delete a status and reassign issues to a new status, workflow rules (such as conditions, validators, and post-functions) are not triggered during this migration. This means automated actions or restrictions tied to transitions won’t execute for these bulk status changes. https://support.atlassian.com/jira-software-cloud/docs/move-issues-to-new-statuses-while-updating-your-workflow/
Project Impact Visibility: The new editor allows you to see which projects use the workflow before publishing changes, helping you avoid unintended impacts.
Testing Recommended: As with any significant workflow changes, it’s best practice to test updates in a staging or small project before rolling out changes broadly. https://community.atlassian.com/forums/App-Central-articles/Best-Practices-for-Managing-Workflow-in-Jira/ba-p/2944228

What to check after Status Updates

Automation Rules: You’ve already checked automation rule JSON exports for references to old statuses, which is excellent. Continue to ensure no automations, filters, or reports reference deprecated statuses.
Status Mappings: Double-check that all issues previously in old or duplicate statuses have been correctly migrated to the new status. Use Jira’s search/filter tools to confirm no issues are left in now-obsolete statuses.
Workflow Rules and Permissions: Review any custom workflow rules and permissions, especially if you previously used advanced conditions or validators that may not yet be available in the new editor.
Integrations: If you have external integrations (e.g., with GitHub, Slack, etc.), verify that they are not referencing old statuses.

All comments

Usman_ju24nf

Hello @Yatish Madhav

Until feature parity is reached, you are encouraged to use whichever editor best fits your needs, and you can set your preferred default editor for convenience.

You can refer to the guide here for Features in the new Workflow

While the new editor is user-friendly, there are some important considerations:

Feature Gaps: Some advanced features and rules are still only available in the old editor. For example, certain conditions, validators, and post-functions-such as "User Is In Group Custom Field," "Field Required Validator," "Looped transitions," "Exporting workflows," and "Triggers"-are not yet supported in the new editor. If your workflows depend on these, you may need to switch back to the old editor to configure them.
Rule Mapping: The new editor groups rules differently (Conditions, Validators, Post-functions) and replaces many old rules with new equivalents. However, not all legacy rules have direct replacements yet.
No Workflow Rule Triggers on Status Migration: When you delete a status and reassign issues to a new status, workflow rules (such as conditions, validators, and post-functions) are not triggered during this migration. This means automated actions or restrictions tied to transitions won’t execute for these bulk status changes. https://support.atlassian.com/jira-software-cloud/docs/move-issues-to-new-statuses-while-updating-your-workflow/
Project Impact Visibility: The new editor allows you to see which projects use the workflow before publishing changes, helping you avoid unintended impacts.
Testing Recommended: As with any significant workflow changes, it’s best practice to test updates in a staging or small project before rolling out changes broadly. https://community.atlassian.com/forums/App-Central-articles/Best-Practices-for-Managing-Workflow-in-Jira/ba-p/2944228

What to check after Status Updates

Automation Rules: You’ve already checked automation rule JSON exports for references to old statuses, which is excellent. Continue to ensure no automations, filters, or reports reference deprecated statuses.
Status Mappings: Double-check that all issues previously in old or duplicate statuses have been correctly migrated to the new status. Use Jira’s search/filter tools to confirm no issues are left in now-obsolete statuses.
Workflow Rules and Permissions: Review any custom workflow rules and permissions, especially if you previously used advanced conditions or validators that may not yet be available in the new editor.
Integrations: If you have external integrations (e.g., with GitHub, Slack, etc.), verify that they are not referencing old statuses.

Yatish Madhav

This is great! Thanks @Usman - appreciate the detailed response.

2 things:

Please can you confirm what to check IF I switch to the new editor BUT the old workflow possible had items in the "Unavailable features" or Feature Gaps?

Eg. if I edit a workflow and switch to the new editor and, unknowingly there was a "Compare Number Custom Field' as example in the workflow and Update it. In these cases, will if give an error OR will it simply overwrite and lose the "Unavailable features"?

How can I check or be updated on 'Unavailable features' becoming available and until feature parity is reached? Is there a ticket I can watch perhaps? (Since I assume there would not be articles, announcements or new features with each of them updating in the new editor)

Thank you

Yatish

Yatish Madhav

Any other thoughts or comments on this post or my last response, please?

Thank you

Yatish

Yatish Madhav

Hi - FYI For anyone who hasn't seen this yet -

Out with the old (workflow editor) and in with the new (workflow editor) posted on 29 Jul 2025

https://community.atlassian.com/forums/Jira-articles/Out-with-the-old-workflow-editor-and-in-with-the-new-workflow/ba-p/3073415?

Inna S

Hi,

late to the party.

Found that they completely removed

- an ability to reuse a transition, so you will have to duplicate it manually, with all the substeps, validations and post-functions

- text view of the workflow, so your ability to search and debug the complex workflows is gone

Mia Tamm _Simpleasyty_

The visual editor is definitely easier for day-to-day changes, but I think losing a compact/text representation is bigger than it looks.

For complex workflows that view wasn't just another way to edit — it was also a debugging and audit tool. Even if the old text view doesn't come back, having some way to inspect the whole workflow structure (and ideally compare changes before publishing) would make the new editor much safer for admins.

Mia Tamm _Simpleasyty_

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

workflow

editor

flow