Hello Jira Software next-gen fans,
My name is Bryan Lim and I'm a Product Manager working on next-gen.
Today, I'm pleased to announce the launch of Workflow Transitions in next-gen. Workflow Transitions enable teams to visualize and map their process into Jira. Let’s consider an example: a scrum master of a software team wants to ensure each task goes through a specific process before it can be marked as Done. For example, a task must go through the following steps for completion: To Do, In Progress, In Review, and finally, Done.
Admins can access the Workflow Editor via the next-gen board. Rules help admins streamline and automate common steps for a team’s workflow; thus, project admins will now need to visit the Workflow Editor to create and edit rules.
Admins can map their team’s process to Jira and ensure work goes through specific status transition(s).
We’ve added three new transition rules to next-gen:
An example of the “Restrict who can move an issue” rule is when a team only wants the Product Owner to move issues from “In Review” to “Done.
Add a rule to a transition via the Workflow Editor:
Restricted transition rule reflected on the board:
Which rule is your favorite?
Dropzones on the board
When transitions are set up, end users understand how work flows on the board via dropzones
Workflow transitions bring you one step closer to mapping your team’s process in Jira and allow you to accurately track Jira issues as they transition from status to status. We’re just getting started with Workflows in next-gen. In summary, keep these two pieces of advice in mind:
Feel free to voice your feedback for these features (or your feedback for Next-gen, in general) on this thread. Check out our public roadmap for what's coming next: https://www.atlassian.com/software/jira/whats-new/next-gen
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event