You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Scenario is that we would want to make sure certain fields are populated for a ticket before a user is able to change the status/pick up a task. For example, before a user is able to move a ticket from the to-do status, we want to ensure that the following have values:
- Fix values
- Custom user fields (which we use to auto-reassign the task for future status changes)
- due date
Hi @Samson Tan, that would best be accomplished by adding validations on the workflow for that issue types you want this to apply to.
You could use the "Fields required" validator and select as many or as few fields as you need. This would ensure that the transition will not proceed unless those fields have values.
Hi @Gareth Cantrell , thanks for the helpful answer. We are using the next-gen board - from my research and viewing on the UI, seems that functionality is unfortunately not available =(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Samson Tan , you're right .. next-gen projects don't yet have editable workflows as classic projects do.
There is a ticket (Ability to edit workflow in Next-gen project) to track this, however there is also a workaround using an automation rule you could try as mentioned by Jesse Geiger in the following thread: Managing Next-gen status/workflows
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the helpful links, Gareth. If I understand correctly, that would help with ensuring a specific path in the workflow, which is good. I've gone a brute force method as Jesse suggested. Not the cleanest, but I suppose it will do for now!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Samson - Or you could migrate that particular project over to a Classic Software or Business project where you can edit the workflow. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John, yes something worth considering.
Part of the reason we were using the next-gen was because it felt more seamless out of the box, without needing to get too deep with configurations. But perhaps we're outgrowing it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can always use a combination of project types. Just migrate over to Classic Software for those projects that need more customization.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
During my 17 years as a coach, mentor, and trainer of Agile teams, I’ve participated in hundreds of Agile planning meetings. The end result was a wall of backlog items annotated by an explosion of co...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.