Restrict users from same group at different status

[Srikanth Mamidala]

Hi team, 

Is it possible to restrict users from same group cannot be assigned at a different status

For example:

Group has 2 members A and B

I have assigned that only group which A and B exists can be assigned at in progress status. Once done it does to review status but at this status user who did the work cannot be a reviewer. 

like if A does the work only B can review it, and if B does only A can review. 

How do I achieve this? 

Thank you. 

[John Funk]

Hi @Srikanth Mamidala  - you could add a custom field and auto-populate it with the opposite person from who is assigned in the In Progress status. Then add a condition for the transition to Review status and choose the User in Custom Field option. Then only the person in that custom field could move it to Review. 

[Srikanth Mamidala]

Thanks John for the idea, however, how do I auto populate the filed with the opp user if they both belong to same group? They could be either of them. 

[John Funk]

where the user is not the assignee.

[John Funk]

In other words, but a post function on the transition to the In Progress status that sets the assignee to the current user (assuming the user is the one who pulls the card to In Progress). 

Then create another post function on the same transition (but later in the process below the one to set the user as the assignee) to set the value of the custom field to the value of the group where where the value != assignee. You might need to use Automation For Jira for that - but it's free now.  :-)

[Srikanth Mamidala]

Hi John, 

Sorry for the late response, I was still not able to figure out how to accomplish this. 

1. I cannot create another post function on the same transition because assignee is option is already been used earlier and it doesnt show assignee option

2. When I use the step at project automation, I cannot use group(only shows users) to set it as != option for the custom field. 

If you have any step by step breakdown on how to do it Id really appreciate 

Only alternative I can think of currently it to make that custom field(peer reviewer) mandatory in the create issue page and use that field as as assignee on the peer review transition but it it will be an issue if we have more number of peer reviewers

[John Funk]

I would go ahead and install the Automation For Jira marketplace app if you have not already done that - it's now free! Don't just use the built in project automation. Then you should be able to accomplish what you need.