Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

DAS Admin
August 29, 2024

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.

2 answers

0 votes
Matthias Wolf-Dietrich
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 11, 2025

We found a way around this issue.

  1. Find the project id of the projects you want to have included. Go to project settings >> details and copy the project id from the address bar (e.g., ...?pid=1234)
  2. Create a filter containing the projects you want to have included, using the project id, e.g., project in (1234, 1235, 1236). Save it. Remember the filter id found in the address (e.g., ...?filter=987)
  3. Share this filter as broadly as necessary, e.g, VIEW for any logged-in user.
  4. Create a second filter, referencing the filter id of the first filter. You can add more criteria if needed, e.g. filter=987 and priority=high.

Even if a user does not have access to projects B and C (1235 and 1236), the filter still works and will display all the tickets they have permission for.

0 votes
Marc -Devoteam-
Community Champion
August 29, 2024

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
August 29, 2024

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?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events