How to Configure Permissions in Jira

Edited 1 week ago by ExtremeHow Editorial Team

JiraSecurityAccess ControlTeam ManagementCollaborationSoftware DevelopmentProject ManagementPermissionsWindowsMacLinux

Jira is a popular tool used by teams and organizations to track and manage projects. One of the key components of effectively managing projects in Jira is configuring permissions. Setting permissions correctly ensures that team members have appropriate access to the information and functionality they need while protecting sensitive and important data. This guide will walk you through the process of configuring permissions in Jira, explaining the different levels and types of permissions and how to set them.

Understanding permissions in Jira

In Jira, permissions are generally classified into three categories: global permissions, project permissions, and issue-level security. Each of these categories contains specific permissions that can be adjusted based on your needs.

Global permissions

Global permissions control what users can do across all projects within the Jira application. These permissions include administrative tasks and are critical to managing the entire platform.

• JIRA System Administrator: This is the highest level of access, allowing users to manage the entire JIRA.
• Jira Administrator: These permissions provide access to most administrative tasks, but not system-level functionalities.
• Create shared objects: This allows users to create dashboards and filters that can be shared with others.
• Manage group filter subscriptions: Users can manage subscriptions for filters that are sent to groups.

Project permissions

These permissions apply to individual projects and control what users can do within a specific project. Each permission can be assigned to different roles, groups, or specific users.

• Browse Project: Permission to browse or view a project and its issues.
• Manage Sprints: Users with this permission can manage ongoing and upcoming sprints.
• View development tools: Determines whether the user can view information related to the development tools integrated into the project, such as commits, branches, and build information.
• Work Issues: Allows you to log work issues and adjust estimates on project issues.

Issue-level security

Issue-level security allows you to control who can view specific issues within a project. By setting the security level, you ensure that sensitive information is visible only to authorized users.

• Security Levels: Security levels apply to different issues. You can create different levels based on the sensitivity of the information.
• Determine issue security: People with this permission can determine the security level of an issue.

How to configure permissions in Jira

To configure permissions in Jira, follow these steps. The explanations and steps here cover managing global, project, and issue-level permissions.

Step 1: Accessing Jira administration

To start configuring permissions, you must have the required administrative access. For global permissions, you need Jira system administrator or Jira administrator access.

After logging in, go to the Jira Administration console. This is usually done by clicking the Settings or Gear icon at the top right of your Jira screen. You will see a menu listing the Administration options. Select "User Management" or "System" depending on the changes you want to make.

Step 2: Configuring global permissions

Global permissions are found in the "Global Permissions" section of the Administration Portal. Once there, you can adjust who has access to high-level features and administration tasks in Jira.

To add or remove global permissions:

1. Select "Global Permissions" from the Administration menu.
2. Click 'Edit permissions'.
3. Use the interface to add or remove groups for each permission. Common groups include 'jira-administrators' and 'jira-users'.
4. Remember, changes made at this level affect all projects in Jira, so consider organizational policies before changing these settings.

Step 3: Configuring project permissions

Project-specific permissions are managed within each individual project's settings. To access them:

1. Navigate to a specific project by selecting it from the Projects menu or dashboard.
2. Click "Project Settings" in the lower-left corner.
3. Select "Permissions" from the Project Settings menu.

In the permission configuration, you'll see a detailed list of permissions available for that project. Here you assign roles, groups, or individual users to each permission.

Modifying project permissions:

1. Locate the permission you want to modify.
2. Click on 'Edit Permissions'.
3. Use the Add or Remove functions to change which groups or users have specific permissions.
4. Project roles are often used to simplify permission management by grouping similar users under the same access rights.

Step 4: Configure issue-level security

By default, all issues in a project are visible to users who have the 'Browse Project' permission. However, you can configure security levels to restrict this visibility.

Creating Security Levels:

1. Go back to the "Project Settings" menu.
2. Select "Issue Protection Plans."
3. Create a new plan if no plan exists, or edit an existing plan.
4. Add different security levels based on your needs.
5. Assign users or groups to each security level, ensuring that only trusted personnel gain access to sensitive issues.

Applying a security level to an issue:

1. Edit the issue you want to restrict.
2. Look for the 'Security Level' field (you may need to customize the screen to display this field).
3. Select the appropriate security level.
4. This ensures that only users with the specified security level can view the issue.

Permission configuration examples

Let's consider some example scenarios to illustrate how permissions can be set:

Example 1: Agile development team

An agile development team may need different permissions for developers, testers, and product owners.

• Developers:
  • Browse projects
  • Work on the issues
  • Create issues
  • View development tools
• Testers:
  • Browse projects
  • Work on the issues
  • Create issues
  • Test issues
• Product owner:
  • Browse projects
  • Manage Sprints
  • View development tools
  • Manage watchers

Example 2: Confidential project

For a project with sensitive data, strict issue-level security can be established:

• Create a security level called 'Confidential'. Assign it only to senior management and specific team leaders.
• Make sure all sensitive issues are marked with 'Confidential' security level.
• Set default project permissions to ensure that only 'Project Administrators' can set or change the issue security level.

Best practices for configuring permissions in Jira

Configuring permissions effectively requires a balance between access and security. Here are some best practices to help you get the setup right:

• Use project roles: Instead of assigning permissions to individual users, use roles. This simplifies management as teams change and grow.
• Check permissions regularly: Review permissions periodically to ensure they are in line with team needs and security policies.
• Limit global permissions: Grant only the necessary global permissions to reduce the risk of accidental or intentional misuse.
• Document security levels: Maintain clear documentation of your security configuration to help manage access and onboard new team members.

Conclusion

Configuring permissions in Jira is crucial to managing both efficiency and security in your projects. By properly using global permissions, project permissions, and issue-level security, you can grant the right level of access to team members, protect sensitive information, and optimize your project management processes. Following the best practices outlined will help ensure that your Jira projects are set up securely, allowing your team to focus on their work without worrying about unauthorized access or data breaches.

  Share This Article

If you find anything wrong with the article content, you can request an update