What's the minimal permissions needed to see that a project exists without seeing issues?

[Matthew Schwarz]

I want to make a filter (and a dashboard showing that filter) that pulls in issues from two different projects. Some people have access to one project, some to the other, and some to both.

I want people to be able to view and dashboard and filter, but only view the issues in the filter for the project they have access to.

Problem is that the filter fails if you don't have access to one of the projects.

Is there a way to give minimal permission to see that a project exists, so that the filter won't fail, but still not let you see any of the issues in the project?

[Nic Brough -Adaptavist-]

You cannot do this.  If an issue cannot be seen by a user, then it is not just not visible to view, but its data will not be returned at all when a filter is run, so it won't feed into any reporting done with the filter.

Imagine for example you have three issues with a number field populated - AAA-1 with 2, BBB-2 with 4 and CCC-3 with 8.  If you have a report that adds them up, then you'll get it showing 14, but if run by another user who say has no permission to see BBB-2, they will get the sum as 10.

[Joe Pitt]

A user has to have at least browse permission, which is the lowest level, to see issues. There is no way for you to do what you want. You need two filters.