nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Controlling access to project summary reports

unknown

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 ?

Accepted answers

Jobin Kuruvilla [Adaptavist]

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

All comments

Jobin Kuruvilla [Adaptavist]

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

unknown

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 ?

Nic Brough -Adaptavist-

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.