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 @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
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
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