Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

block assignment outside of user group

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.

 

1 answer

0 votes

Hello @JasonH Arvato

Thank you for reaching out.

Indeed, the property jira.permission.assignable.group should work to restrict your users to only assign issues to users in a specific project. Can you please provide us with a screenshot displaying how you have configured it?

These would be the steps to configure the property:

1 - Navigate to your project > Project Settings > Workflows > Click to edit the relevant workflows

2 - On Diagram mode, click in the status you want to block your users from assignee to other groups > Properties

Screen Shot 2019-11-20 at 18.39.20.png

3 - Add the following:

Property key = jira.permission.assignable.group

Value = team_a

4 - Publish your draft

 If the steps above do not work for you, try the following:

1 - Navigate to your User Management > Groups > Click in the group you want your users to transition the issue > Check if the URL their related ID and paste it in the property value instead of the group name 

2 - Doublecheck the users in group B are not added to group A

Let me know if you have any questions.

Hi Petter, 

Setting fixed properties against the status will not work here.  I need to do it programmatically depending on the current user's group.  

I have components which auto-assign to people in either team A or team B.  If the component auto-assigns to a user in team A then I don't want the user to assign to someone in team B.  If the component means someone in team B gets it then team A should be excluded.

I tried a transition post function, after auto-assigning to the component lead I then made a check on the current assignee's group like this (pseudo code not actual!)

if currentAssignee is a member of teamA then

set jira.permission.assignable.group=teamA

if currentAssignee is a member of teamB then

set jira.permission.assignable.group=teamB

but in both cases I saw no change, all users were in the assign dropdown regardless of group.

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.

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?

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...

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

☕️ Monday coffee with Jexo: Weekly Atlassian news roundup | 21st June 2021

Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...

59 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you