block assignment outside of user group

Question

I have 2 teams of users - team A and team B.

I want to stop members of team A assigning to members of team B and vice versa and force them to use the existing workflow transitions to move issues between teams.

I've tried programmatically setting the  jira.permission.assignable.group property but it seems to have no effect.

Ideally the assign user list would only contain their own team's co-workers, this would encourage them to looks for a workflow option.

JasonH Arvato · Answer

Hi @Petter Gonçalves

I tried using a groovy script in a transition post function to try to set the workflow property so that the next attempt at assignment was within the assignee's group.

Having 2 issue types won't work, it would be very cumbersome and the users creating the issues won't know which type to use.  The group A or group B decision is based on the component lead being used for auto-assignment, so until the issue reaches auto-assigned the issue is not assigned to either group.

I actually have 3 different issue types in and 4 projects sharing the same workflows here.  I really just need a simple programmatic decider -
if currentassignee is member of group A then only allow assignment to their colleagues in group A

if currentassignee is member of group B then only allow assignment to their colleagues in group B

etc...

Petter Gonçalves · Answer

Hello @JasonH Arvato

Thank you for the details provided.

About the post function you mentioned above, what is the app you used to create it? I'm not aware of any apps with post functions that would enforce workflow properties unless you just used the post function to transition the issue to a status with that property.

Anyway, I think that the only option using only JIRA to achieve your need would be to use two different issue types to assign issues for each group. Explaining it better, you would create two issue types and set two different workflows, configuring the "jira.permission.assignable.group" property in all the statuses and transitions of their respective workflows. Would this be an option for you? Or you have more teams where you would like to apply this same logic and the creation of a single issue type for each of them would require a very cumbersome effort?

JasonH Arvato · Answer

Hi @Petter Gonçalves

Any idea on this one?  As described above the requirement is to set it programmatically not just in the workflow status properties.