Controlling access to project summary reports

If I have a permissions scheme that provides the Browse Projects privilege, how can I prevent a role or user that has that privilege from generating summary reports of issue status etc from the project Summary page ?

1 answer

1 accepted

0 votes
Accepted answer

You can't. Not without modifying the JIRA source. Anyone with browse access can generate reports and search for those issues.

Thanks for that. I presume that I am correct in my understanding that a user can't create or edit issues in a project unless he has Browse Projects privilege for the project ?

Actually, it is possible to set it up so that people can create issues without then being able to see them. As this is immensely annoying and confusing for the users and causes a support call for almost every single issue creation, I simply don't do it. I suspect it's the same for edit, although I don't think I've ever seen that tried.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,385 views 15 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you