Hello,
I am looking for an OOB solution for the below requirement.
1. A validation to prompt a user to change the Assignee when a Story transitions from "In Dev" to "In QA".
2. This is extension of the above. Assignee in this case has to be chosen from a predefined list (dropdown list) of testers which show up during the above transition. I repeat, by dropdown list I mean a predefined list of users, not the assignable user list based on all those who have access to Jira.
Any help would be highly appreciated!
Regards,
Mohajit
try this...
1) add a Field has been modified validation to the transition from In Dev to In QA for the Assignee field
2) use the jira.permission.assignable.group property key on the In Dev status and have a group defined that has the QA users included
FWIW...here is a thread where I learned about #2 - restrict-assignee-based-upon-workflow-transition
Thanks, Jack for the solution. Much appreciated.
Just a small clarification.......if I use jira.permission.assignable.group property key on the "In Dev" status and have a group defined that has the QA users included, then will it not deny me to change the assignee of the story to another developer in a situation where the present developer is going on leave and he wants to assign it to another developer?
How and where do I define jira.permission.assignable.group property value?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, regarding the first step mentioned, do I need to select anything from the Available groups as highlighted in the attached screenshot?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.