Can I have two transition options when I move statuses?

[Jason Chayer]

In our workflow, if an issue is not passed in Testing, we can move it back to In Development. However, it does not always move back to In Development because it fails  testing. But, it could move back because the spec changed.

So, is there a way I can have two transitions in this workflow back to In Development, which would allow the tester to choose a reason the issue was moved back?

[Isaac Montes]

Hi Alex, I would look in to your project Field configuration and see if you find a field called work type, if you find that the field is not required, next step is to check the workflow for a validation on the action you are taking, whether is a transition or issue creation.

https://confluence.atlassian.com/adminjiracloud/specifying-field-behavior-776636443.html

https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html

[Alex Scott]

Found out a co-worker altered the workflow/templates for all projects by requiring a new field. He thought he was only changing the workflow/templates for his project. That's good feedback and concerning that someone can make global changes without realizing it.

[Isaac Montes]

Audit log in JIRA administrative menu is a good way to see if there have been any configuration changes. Glad you got it resolved. 

[Nic Brough -Adaptavist-]

This is why you should have very few admins and change control in place.