To understand how users see access to Jira, specifically in the context of being able to view issues within a project, it's primarily controlled through project permissions. Permissions determine what a user can see and do within a specific Jira project.
For users to "see access" in the sense of being able to view issues in a Jira Service Management project, you typically grant them the necessary permissions, such as the Browse Projects permission. This allows them to view the project and its content, including issues.
Here's how you can configure permissions to give users the ability to view issues in a service project, based on the provided reference:
Configuring Permissions for Viewing Issues
Granting the Browse Projects permission to specific users or groups allows them to see the project listed and view its issues. The reference outlines steps for configuring this access within a Jira Service Management project:
- Navigate to Project Settings: From your service project, select Project settings.
- Access Permission Schemes: In the project settings menu, find and select Access, then navigate to Project permissions. This is where you manage who can do what in your project.
- Edit Permissions: On the Project permissions page, look for the Actions menu and select Edit permissions. This puts the scheme into edit mode.
- Locate Browse Projects: Scroll down the list of project permissions and find the Browse Projects permission. Select Edit next to it.
- Grant Access: Under the Granted to section for the Browse Projects permission, select Application access. This option typically grants the permission to users who have access to the specific Jira application (like Jira Service Management). You can also grant permissions to specific groups, project roles, or individual users depending on your configuration needs.
Why Permissions Matter for "Seeing Access"
- Visibility: Users who do not have the Browse Projects permission for a specific project will not be able to see the project listed and therefore cannot access or view its issues.
- Control: Project permissions schemes provide granular control over who can see and interact with your project and its issues.
- Different Levels: Beyond just browsing, permissions control various actions like creating issues, commenting, editing, resolving, and more. "Seeing access" can also imply the ability to perform these actions, which are controlled by other specific permissions.
By configuring these permissions, you are effectively defining who can "see" or access the project and its contents in Jira Service Management.
