Why can users not access filter including projects they cannot access?

[DAS Admin]

The scenario here is that a manager of multiple projects has a singular filter for their three main projects, we'll call them Project A, Project B, and Project C for now, and they have shared this filter all of these projects.

Filter JQL: "Project in ("Project A", "Project B", "Project C")"

I've also tried "Project = "Project A" OR Project = "Project B" OR Project = "Project C"

If User A is a member of Projects A, B, and C, then they can access the filter.

If User B is a member of Project C only, they cannot see any filter results at all, and there is a warning that " 'Project A' does not exist for the field 'project' " and " 'Project B' does not exist for the field 'Project' "

However, if User B looks at a Kanban board (or scrum board) which uses the exact same filter, then they are able to see all issues from Project C (not the other two).

Why is this the case? The permission model seems inconsistently applied.

Ideally, I want to have a filter which can be used by any user to access only the issues in the projects they have access to.

Any help or suggestions appreciated.

[Marc - Devoteam]

Hi @DAS Admin 

This is because the board is part of a project and a filter is not and board filters are mostly shared with the project and not a group or role.

If you create a filter, share them with the projects and not role, group or user.

[DAS Admin]

Hi @Marc - Devoteam

The filter in shared with each of the projects, not individuals or groups, I realise the mistake in my wording and will correct it.

The edit screen shows:

Viewers

Project: Project A

Project: Project B

Project: Project C

 Any other suggestions?