I'm looking for browse permission bug workaround

Question

Hello.

There is a known bug for Jira Cloud (maybe server too?) when in Browse permission for project are one of: Current assignee, Reporter and User custom field value then name of your project is visible for everyone who has access to your instance. That's independent if he has Browse permission for that project or not but name of that project is visible. So, it's pretty annoying when you share one project for your client for example and he can see a lot of other projects names where you used as I said Current assignee, Reporter and User custom field value in Browse project permission. Do you know any workaround for that? I've tried to use workflow properties but without effect. The most useful for us is User custom field value in Browse project permission for example when we want only one time access for particular issue. The biggest question is - how can we still use that without sharing our project names for everyone?

Thank you in advance for any help.

Mateusz · Answer

Thank you for your answer Jack.

Here you can find that bugs: https://jira.atlassian.com/browse/JRACLOUD-37117 and https://jira.atlassian.com/browse/JRACLOUD-34389

Browse project permission for Current assignee give us posibility to share issue for person who is necessary to work on that issue without granting access to rest issues inside that project. How you solve problem when you want to give access for particular issue without revealing the rest of your project?

My permissions are always focused on specific users/groups/roles.

Ok, now I am a curious man :)  what about situation when you gave Browse project permission for specific user but there is a moment when user for example will change team or department in your company and now access for previous projects should be denied. How can I find that specific permission schemes in a many projects in our instance where user XYZ has Browse project permission?

Jack Brickey · Answer

Hi Mateusz, you mention there is a known bug. Do you have a reference from JAC that captures this as a bug? TBH, I can't understand the use of current assignee. Have never any considered something like that for permissions. Can you illustrate this more completely for me and why this would be used? Just curious I guess. My permissions are always focused on specific users/groups/roles.