Is it possible for a jira user to have only read-only access to all the projects and issues within?

Mohit Edupuganti_eu33xi

I have created a user group for each project and each project has a permission scheme assigned to it. Now, there is a new jira user who needs to have only read access/view-only access to all the projects and issues within them. This new jira user should not be able to create, edit tasks, add comments in the tasks and make any changes in the projects. In the permission scheme I assigned only one permission - Browse projects to the new user to achieve this requirement. But the new jira user is able to create a new tasks in the projects.

Ugnius Aušra

Hello @Mohit Edupuganti 

Yes, this is possible, but the confusion comes from where Jira actually decides who can create issues.

Think of Jira permissions like multiple doors.
You closed one door (the permission scheme), but another door is still open.

Even if you only gave the user “Browse projects”, Jira will allow issue creation if the user gets that permission from anywhere else.

Most common reasons:

• The user is still in a project role (Users, Developers, Members, etc.)

• That role still has Create issues permission

• The user is added automatically via default project roles

• In Service Management projects, the portal can allow creation outside the permission scheme

So the permission scheme alone doesn’t tell the whole story.

What usually fixes it:

1. Remove the user from all project roles

2. Create a dedicated role like Read-only

3. Give that role only:

   • Browse projects

4. Double-check with Permission helper

Once the extra role or group is removed, the user will instantly lose the ability to create issues.