Old workflow editor sunset

[#1]

Starting June 2026, we will begin removing the old workflow editor and transitioning all customers to the new workflow editor.

Why are we doing this?
Many years ago, we introduced the “new workflow editor” in team-managed spaces to provide customers with a more modern and intuitive workflow experience. However, at the time, the new editor did not have many of the capabilities supported in the legacy experience, now known as the “old workflow editor.” Over the last 3 years, our team has been working hard to ensure feature parity between the old and new workflow editors, in both team-managed and company-managed spaces – and we succeeded!

Today, over 84% of users publishing workflows are doing so in the new experience! With the positive feedback we are receiving and the usage trends we are seeing, we have made the decision to deprecate the old workflow editor so that we can shift our focus and invest in further enhancing the new workflow editor experience. This means you can expect even more innovative features, improved usability, and ongoing updates that will help your teams work smarter and more efficiently.

(Re)Introducing the new workflow editor!
We believe the new workflow editor offers a powerful experience that makes representing work processes, streamlining workflows, and managing unique ways of working easier than ever. Jira admins can expect the following in the new workflow editor:

✨ An all-in-one modern interface: All workflow actions are consolidated into a single, easy-to-use, visually modern interface – no more navigating across multiple tabs.
✨ A faster, more efficient editing experience: Add, update, or discard changes instantly, with the ability to publish modifications immediately. Streamlined publishing and editing mean admins can make changes without extensive navigation or complex procedures.
✨ A lowered learning curve: Designed to be more approachable for new admins, with less technical jargon, more in-context help, and Rovo skills to edit your workflows with AI.
✨ A text view: For the most complex workflows, the new workflow editor is now equipped with a text view for workflow editing.
…and so much more!

Thank you
We know that change is not easy, but we are confident that the new workflow editor will make workflows visually clearer, simpler to learn, and quicker to update. Thank you for your understanding and for helping us improve the Jira experience!

As always, we welcome your feedback. If you see ways to improve the new editor or face blockers transitioning from the old one, please raise a support ticket Atlassian Support, or reach out to us directly via the feedback button in the bottom left of the new workflow editor. Ensure you select “Atlassian teams can contact me to learn about my experiences to improve Atlassian apps and services” so we can follow up.

Learn more about the key differences between the new and old editors What is the new workflow editor? | Atlassian Support.

---

FAQ

Q: Can I access the new workflow editor now?
Yes. If you are a Jira admin, you will be taken to the new workflow editor by default when editing a workflow. If you have previously set a preference for the old workflow editor, you can access the new workflow editor or update your preference from the “switch editor” dropdown in the old workflow editor.

Q: When will I see these changes on my site?
We'll start removing the old workflow editor from June 11, 2026.

Q: Will I need to “migrate” my workflows from the old editor to the new editor?
No. Today, you can update your workflows in both the old and new workflow editors. Once the old editor is removed, you will be able to update your workflows in the new editor.

[Jean Gordon]

Who has tested this change and why change something else that works?

The constant changes that don’t work for projects and make everyone’s jobs worse are ridiculous. 

Have you checked accessibility and performance as Jira and confluence are no longer good so cannot be used during standup.

Another unnecessary change rather than fixing actual issues like bulk cloning of issues which would actually help. 

[Yatish Madhav]

This is great! Thanks @Swarna Mehta  and Atlassian!

[Dirk Ronsmans]

@Swarna Mehta ,

With the new workflow editor becoming the default editor I'm wondering if there are any plans to include a way to "draw nicer transition lines".

A common request is to make the workflows clearer and more readable. One part that can still be improved is how the lines are being draw between statusses. 

Therefor I wonder if any work is being done to allow admin's to draw their own transition lines or at least add your own waypoints to create proper readible workflows?

[Swarna Mehta]

Hi @Dirk Ronsmans 
We are working on improving the new workflow editor even further. I would love to understand your needs around drawing nicer transition lines.
If you are available over the next few weeks, feel free to schedule a call through this link with me and I'd be happy to bring the insights to our development team: https://calendly.com/meetssm/jira-customer-calls

[Swarna Mehta]

Hey @Jean Gordon 

I understand you have broader issues that need addressing. I could potentially connect you with product managers working on accessibility and performance for Jira. Would you be interested in the same?

[Eglė Kaziulionytė]

Will this new editor handle the cases where we have a heavy usage of plugins? E.g. at least now it is impossible to use new editor if you're using Scriptrunner (or any other plugin) postfunctions  - all those are named the same and it is not possible to distinguish each unless you open each and every post function individually (and ofc you forget what was the previous postfunction unless you can memorize more than 10 at once :D ). Ultimately it increases admin effort to do even small change (or simply check how workflow operates) several times! Not sure how enterprises (or companies that use one or another plugin) will deal with such a terrible change... 

[Robert Eiser]

I have been enjoying the new editor, it is a nice improvement. I second @Eglė Kaziulionytė - when we are using add-on conditions, validators and post-functions in the new editor it is difficult to tell them apart without opening them up - it would be helpful if there was more context displayed for these actions in the sidebar.  

[Swarna Mehta]

We hear you @Eglė Kaziulionytė and @Robert Eiser
Some of these fixes are on Atlassian's side, but some are actually require the third party app to change what information they allow us to surface in the new editor. We are working with the apps to improve their experience with the new editor.
I would request opening a support ticket describing the problems in detail so that we can make the case stronger across al stakeholders: https://support.atlassian.com/contact/#/?inquiry_category=technical_issues&support_type=customer

[Robert Eiser]

Hi @Carol Low and @Eglė Kaziulionytė it looks like there is already a ticket open for this https://jira.atlassian.com/browse/JRACLOUD-96131 

[Eglė Kaziulionytė]

Thanks @Robert Eiser 

This just proves that those changes are hasty and without proper testing. Why the good working solution should be sunset? :(