How to prevent people that dont match the query from showing up in a kanban board filter list

[wes christiansen]

We've got a filter that says 
assignee in (list of people) AND project in (list of projects) ORDER BY Rank ASC

The filter seems to do the job effectively.  However in the list of people avatars, next to the quick filters, more than a dozen people are listed who are not in the "list of people".  How can I prevent people who are not in that list, from having their avatar show up in the filter section?

[Nic Brough -Adaptavist-]

The avatars in the quick-filter area represent the list of people who might be assigned an issue, it's nothing to do with the board filter.  If you want to remove people from that, you'll need to take away their permission to be assigned issues.

[Jack Brickey]

I may be wrong here as I have been meaning to check this casual observation I had awhile back. It seems that if the avatar is present then it means the user has one or more issues on the board. If the issue assigned to them is removed then their avatar disappears. Again I need to test.

[Trudy Claspill]

I concur with @Jack Brickey 's observation; I see the same thing.

The permission scheme on our Classic project allows any logged in JIRA user to be assigned to an issue, but avatars are displayed only for users who are actually assigned to an issue.

[wes christiansen]

On my board there are 6 people who are assigned tickets and 18 people displayed.  So if you click on 2/3 of the people as a filter, nothing will display.

[Trudy Claspill]

I just did a quick test where I created a filter

assignee in (user1, user2) and project in (project1, project2)

...where the two users each have issues assigned in project1, but in project2 only user1 has assigned issues. user2 does not have issues assigned in project2. In both projects other users not included in the filter have issues assigned.

When I created a board from that filter, a third user (user3) who has issues assigned in both projects was included in the avatar selection filter.

There are two other users (user4 and user5) that are assigned to issues in both projects. I observed that the difference between user4/user5 and user3 is that user3 has not-Done issues assigned to him in both projects while user4 and user5 have not-Done issues in only one or the other project.

Not sure if that observation is meaningful.