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

Issue Alternative Assignee - problem with user filtering

Fyodor Jan 07, 2015


We detected a problem using user picker from project role.

This field ignores user filtering.


Group "A" was added to project role "tester"

Group "B" was added to user filtering for this field

There is a user who is a member of "A" group but is not member of "B"

The user picker from project role field was added to screen for selecting users from role "tester".

So I assume that this user will be not displayed in this field on a screen. However the field offers to select this user. I am able to select this user and assign issue to user.


is there a bug or wrong configuration?

JIRA version: 6.2.5

Issue Alternative Assignee plugin version: 1.7.5





2 answers

1 accepted

0 votes
Answer accepted
Nic Brough [Adaptavist] Community Leader Jan 08, 2015

You have set the field to show users from group A or role of Tester.  Your user matches that rule, so they are offered as an option.

Fyodor Jan 08, 2015

Hello Nic >>You have set the field to show users from group A or role of Tester. Group A (this group was added to role) contains also users who should not be selectable in my case So I suggest that I should use user filtering to limit available users, users in role "Tester" (see selected role from screen) AND user that matches group "B" (see user filtering from screen). However it is not working

Nic Brough [Adaptavist] Community Leader Jan 08, 2015

I'm not sure I understand this. You've set the field to say "group A or role of Tester". You've then added people you don't want to list into group A or the role of Tester. Either remove them from the group or role, or change the setup of the field. Basically, it's your usage of the group / role that is the problem here - sounds like you need to break it up into more groups and use them differently.

Fyodor Jan 08, 2015

Yes, the workaround is to create new group that matches A and B. However it is not global solution. I see that there are user filtering functionality, so I assume that it should work, however it doesn't. It seems this is a bug.

0 votes
Fyodor Feb 10, 2015


Is there any other suggestions regarding this problem ?




Nic Brough [Adaptavist] Community Leader Feb 11, 2015

Not really, your group setup is incorrect, you can't work around that without putting something in place for Jira to work with.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira Software

Early Access: If you use Jenkins and Jira Software Cloud, you need to read this!

The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...

263 views 0 8
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