Forums

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

Is it really true: Without "Browse Project" a assignee kann literally do nothing on an issue

Hans-Joachim Fritz
Contributor
January 18, 2022

I have a wonderfull daily work project. I want to assign issues to my colleagues to work on. Surprisingly the aren't able to follow the link they received via emal as notification about the assignment - no access rights, despite the fact that they have all access rights via permission schema.

So what is "Browse Project" good for, if it is mandatory for even seeing an issue?

I don't want them to see other issues within this project, just the issue one is supposed to  work on. 

 

 

4 answers

4 accepted

2 votes
Answer accepted
John Funk
Community Champion
January 18, 2022

Hi @Hans-Joachim Fritz 

You can use issue level security to hide certain issues from certain users. But all users who need to see any issues on the project will need Browse Project permissions. 

2 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 18, 2022

Yes, "browse" means "can read the issues in the project" in general.

You have to have that, otherwise, you can't limit people to their own set of projects.  That's what it is good for - controlling access to projects.

>I don't want them to see other issues within this project, just the issue one is supposed to  work on. 

You will need to impose an issue security scheme on the project.  In the most simple case, add a single "level" to the scheme, with a name like "restricted" and set the level to say "only assignee, and others who need to see it (reporter, team lead, etc)".  Then default the level and apply it to all the issues in the project.

1 vote
Answer accepted
Nayana N
Contributor
January 18, 2022

Hey @Hans-Joachim Fritz ,

Yes " Browse Project " Permission is mandatory to access project and to view issues in that project.  Without  " Browse Project " Permission they can't access the project. And for your requirement you can use issue security level. 

0 votes
Answer accepted
Marcel Plomp
Contributor
January 18, 2022

I added a "multi user picker field" to the screens and provided the browse permission for that field.

Any user in that field can now see the related issue AND only that issue.

I'm not sure anymore if this field type is/was available out of the box or provided by an add-on.....

000255.png

Hans-Joachim Fritz
Contributor
November 22, 2022

Thanks a lot, I haven't tried yet, but at least it's a way mentioned on related issues. From time to time I do stumble over the missing functionality

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events