Which Jira Permissions Are Required to Set Up a Connection?

To set up a successful integration with Jira for Defects and Requirements, the required Jira permissions depend on whether you are connecting to Jira Cloud or Jira Server. Jira permissions are managed in Jira. For more information about managing permissions in Jira, refer to Managing permissions on the Atlassian support website.

Activating Jira Service Desk can affect allocated Jira permissions.

Jira Cloud required permissions

To connect to Jira Cloud, you are required to have the following permissions:.

  • Jira Administrators global permission

  •  Site Admin and Project Administering permission for the Project

    • If the user does not have Site Admin permission, an error message will appear: "Webhook cannot be registered."

    • If the user does not have Project Administering permission, but does have Site Admin permission, an error message will appear: "Project Administering Permission is required for Project: <Jira_Project_Key>."

Jira Server required permissions

To connect to Jira Server, the following permissions are required or recommended.

  • (Recommended) Jira Administrators global permission

  • (Required) Create Issues permission and Link Issues permission for the mapped Projects for mapping Jira issue types

  • (Required) Browse Projects permission in the mapped Projects

  • (Required) Edit Sprints for a Project

Permissions will be validated by each Project. If the user has changed the Connection URL and the Issue typemap no longer matches the URL, then the user should be able to Save the connection as usual. When the user has saved the connection and opened the Jira Integration Config page, a warning message will appear: “Connection URL has been changed. Please update your issue mappings accordingly.”