How to use automation to ensure that certain fields of the ticket are populated?

[Samson Tan]

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

[John Funk]

Hey Samson - Or you could migrate that particular project over to a Classic Software or Business project where you can edit the workflow.  :-)

[Samson Tan]

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.

[John Funk]

You can always use a combination of project types. Just migrate over to Classic Software for those projects that need more customization. 

[Gareth Cantrell]

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.

[Samson Tan]

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 =(

[Gareth Cantrell]

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

[Samson Tan]

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!