You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I’m Yuan, a Product Manager on Jira Cloud’s workflow team. We’re excited to announce that we’re working towards a single workflow editor by combining the team-managed workflow editor’s ease of use with the company-managed workflow editor’s power and flexibility.
We’re looking for admins and marketplace developers to help us make our workflow editor the best it can be. If you’re interested, join our focus group to work with our product team as we progress.
Over the next year or two, the team will focus on feature parity between the two workflow editors. More specifically, we plan to add advanced features that currently only exist in company-managed workflows (like the advanced validator, conditions and post functions) to team-managed projects. In the end, the workflow editor in both team and company-managed projects will be almost identical, the key difference being that company-managed workflows can be shared across projects using workflow schemes. (Note: we do not plan to make changes to workflow scheme as part of this work)
We heard that switching between two different workflow editors across two project types can be challenging, so we’re creating one workflow editor with:
🌎 The best of both worlds: Admins will no longer need to make the tradeoff between the easier-to-navigate UI in team-managed projects and the richer features in company-managed projects. You’ll have both.
🔄 Less context switching: With a single workflow editor, admins can better focus on what they do best: customizing Jira to suit the unique needs of their team and onboarding new users. No more thinking about which workflow editor works which way.
🌱 Better extensibility: Unifying our private and public workflow APIs unlocks more of Jira’s power to Atlassian Marketplace apps and further builds on our ecosystem.
Our roadmap’s details are still being finalized, but here’s what you can expect:
If you’re an admin of a team-managed project, look out for new features in the workflow editor.
If you’re an admin of a company-managed project, there won’t be many changes just yet. Meanwhile, you can go to a team-managed project and familiarize yourself with the workflow editor’s UI to get a headstart on the changes.
If you’re a marketplace developer, you’ll gradually receive access to more public workflow APIs.
Our team is very excited about building a better workflow editor that’ll power both project types and we'd love to hear your thoughts. As I mentioned before, you can join our focus group and work with us on building this new experience.
If you have questions, comments, feedback, or requests, I’d love to hear from you. Either drop a comment here or email me directly at firstname.lastname@example.org. And don’t forget to watch this page to keep track of any updates. We’ll make sure to add any important information here.