#Jira client reports read only software

ensure permission Browse Projects and Administer Projects is not set to 'Any logged in user' or to users with only 'Application access' to Jira.Go to Settings> Issues > Permission schemes, and for every permission scheme in use (for all projects):.

Under Add Project Role at the bottom of the page, enter your desired role's name (example: readonly-users-role) and a description. In Jira, click Settings (cog icon) > System.

Go to Jira and create a new project role for the external users (example: readonly -users-role).

Add the external user(s) to the readonly -users group only.

Choose the newly created group from the list.

#Jira client reports read only software

Click Add group for the target product (like JIRA Software or Jira Work Management).Go to User Administration > Product access.Create a new group (example: readonly-users) and grant it product access to Jira.Go to your site's User Management Groups page (.Let's break this into steps: Create a Group To achieve this, we'll need to create a group, project role, and make changes to all projects' permission schemes. There are quite some steps to getting this done, but it is very possible. We will need to restrict all projects to your internal users, and then grant specific permissions to the external users. Allowing anonymous project visibility means the project is publicly visible on the internet, whereas using read-only users will require users to have an Atlassian account, a Jira license on the site, and for them to log in to the site to view the project. This approach is different than managing anonymous or public access.