Final notice: old workflow editor deprecation in July 2026

[#1]

---

Previous posts:

Default Experience: New Workflow Editor

Old workflow editor sunset

---

Starting 13 July 2026, we will begin the final removal of Jira’s old workflow editor. This rollout will complete by 26 July 2026 through Jira’s seasonal releases.

Over 95% of all customers already publish their global workflows from the new editor with growing trends every week. With a future of more powerful workflows ahead, we’re completing the transition and removing the old editor so we can keep improving a single, modern workflow editing experience for Jira admins.

If you still use the old workflow editor, now is the time to get familiar with the new experience.

Why we’re making this change?

Over the last few years, we’ve invested heavily in bringing the new workflow editor up to parity with the old experience while making it faster, clearer, and easier to use. This transition lets us focus our investment on one editor instead of splitting effort across two experiences.

That means admins can expect ongoing improvements in one place, with a more modern interface and a simpler path to building and maintaining workflows.

What this means in practice

Once the deprecation rollout is complete, workflow editing will happen only in the new workflow editor with no option to switch to the old editor.

What’s happening and when?

The final deprecation rollout will begin on 13 July 2026 and complete by 26 July 2026 through Jira’s seasonal releases.

• “Open Workflow in old editor” option in the new workflow editor will be removed during this window.

• The old workflow editor will no longer be available.

• You do not need to migrate your workflows. Existing workflows will continue to work and can be edited in the new workflow editor.

Why the new editor is ready?

The new workflow editor is already the primary experience for most admins, and over 95% of customers publish their global workflows there today.

If you have not used it recently, the new editor includes:

• A modern, all-in-one editing experience that reduces tab switching and makes workflow structure easier to understand.

• Faster editing and publishing so admins can make updates more efficiently.

• Text view for complex workflows when you want an alternate way to inspect and edit workflow logic.

• A lower learning curve with clearer language and more in-context guidance.

Recent improvement

You can now preview marketplace transition rules in the new workflow editor. We’re also working further on a “View all” experience for rules that’s coming soon to make these rules even easier to inspect.

Get familiar with the new workflow editor

We know change can take time, so we encourage admins to review the available resources and get comfortable with the new experience now.

• What is the new workflow editor?

• Video walkthrough and key differences in the new workflow editor

Got feedback?

We continue to invest heavily into workflows in Jira to make it a state of the art solution to best capture your business processes and allow working with AI agents, users and 3P apps. If you run into blockers while using the new workflow editor, please raise a support request through Atlassian Support.

FAQs

When will this change happen on my site?

The final deprecation rollout will start on 13 July 2026 and complete by 26 July 2026 through Jira’s seasonal releases.

Can I still use the old workflow editor?

The old workflow editor is being fully deprecated during the rollout window. After the rollout is complete, workflow editing will solely happen in the new workflow editor.

Do I need to migrate my workflows?

No. You do not need to migrate your workflows. Your existing workflows will remain available and can be edited in the new workflow editor.

Where can I learn the differences between the old and new editors?

You can review the support documentation and the video walkthrough to get familiar with the new experience.

[Tim Eddelbüttel]

That’s one of those improvements that simply polarizes opinion.

I really don't get, why the conditions / validators / post-functions are remapped like they are remapped.

[Richard Scholtes]

I think it's unfortunate, that you're not giving yourselves the time to solve at least the biggest gaps like: Approvals not being restrictable, new rule structures limiting your pacing even more and making the process vulnerable to racing conditions. That's not a good timing for a switch in my opinion.

[Josh]

The new editor requires some relearning and adjustment, especially from long-time admins, but it seems like an improved experience all the way around.

Hopefully some time is reserved for after the initial launch to address some of the quality-of-life improvements that Tim, Richard, and likely others will surface.

[Kristin Lyons]

I've been strictly using the new editor for some time now but still prefer the old editor, in the old editor it seems like the logic was better explained.

[Darryl Lee]

One of my users pointed out today that previously, if Admins had not "cleaned up" your workflow diagram, users could still drag and move steps a "read only" mode while in Issue View to try to understand how a tangled workflow actually worked.

But seriously, with all the AI advances, Workflow Editors still can't untangle spaghetti workflows?

Rovo: make this workflow diagram readable

With Atlassian's increased concern over aesthetics and design, it's surprising they didn't make automatically "cleaning up" a workflow diagram like this into a priority:

Source: Worst Jira Admin Contest: A Thousand Transitions 

Now that I look at it, I think @Rachel Wright probably did try sorting it out. Woof.