Define JIRA roles/permissions

[Sophia Tamaki]

Hi,

Could someone please provide a description of each of the roles listed below? Thank you. 

- Administrators

- Browse

- Developers

- External Developers

- Notifications

- Reporters

- Support

- Users

[Jad Icc]

Here's a quick rundown of common JIRA roles/permissions:

• Administrators: Full control over the project, including permissions, workflows, and configurations.
• Browse: Allows users to view the project and its issues.
• Developers: Users who work on and resolve issues, typically with access to transition workflows.
• External Developers: Limited access, often restricted to specific issues or features.
• Notifications: Users who receive updates about project activities or changes.
• Reporters: Individuals who create and log issues in the project.
• Support: Handles queries, tracks bugs, and ensures resolution for support-related issues.
• Users: General access to interact with the project, depending on assigned permissions.

Just like how "infection control experts" ensure each team member has specific roles for effective management, understanding JIRA roles ensures clarity and efficiency. Let me know if you need further help!

[Sophia Tamaki]

Thank you Jad. Great overview!

[Akash Singh]

@Sophia Tamaki Welcome to Atlassian Community!

Jira, out of the box, comes with only two predefined roles: Administrator and atlassian-addons-project-access (a system role). The roles mentioned in your post—Administrators, Browse, Developers, External Developers, Notifications, Reporters, Support, and Users—appear to be custom roles created by your Jira Product Admin.

Key Points about Roles in Jira:

1. Roles vs. Groups:

   • Roles are project-specific, while groups are global.
   • Project Administrators can manage roles, but groups require Jira Administrators to update.

2. Role Functionality:

   • Roles themselves don’t define permissions; permissions are linked via the permission scheme or issue security scheme for each project.
   • For example, if a role is assigned to the "Browse Projects" permission in the permission scheme, users with that role can view issues in the project. Without this link, adding someone to the role won't grant them any capabilities.

3. Custom Roles:

   • These roles are often created to organize users based on project needs, such as Developers for team members working on code or Support for those providing assistance.

For a detailed explanation of Jira permissions and roles, you can refer to these resources:

• Overview of Jira Cloud Permissions
• Manage Project Roles

If you'd like a specific breakdown of what each custom role might represent, I recommend reaching out to your Jira admin for clarification, as the roles and their purposes can vary by organization.

[Sophia Tamaki]

Thanks so much for the response Akash, this is very helpful.