Permissions for Integration User on Jira

  • Category : Permissions
  • Article Number : 14
  • Publish Date: 24 Jun, 2024

Objective

In this article we will explain-

  • Integration user and its importance in Sinergify

  • All the necessary JIRA permissions for the JIRA Integration User

Integration User & Its Importance

Integration user is an actual user that exists in Jira. Authentication on Salesforce Instance screen is done via this ‘Integration‘ user. This user plays an essential part in data flow between the two platforms. Hence in order to attain the features available on Jira Platform within Salesforce it is necessary:

  • To use a unique name as per the business requirement so that it is identifiable via the business teams or end users. For e.g. “Jira-SF Integration User”, “Sinergify User”, “ SF User” etc.

  • To provide the necessary permissions to this user in Jira Environment as per requirement.

Necessary Permissions for Jira Integration User for Company managed projects

JIRA Integration User does not necessarily require Administrator privileges.

Salesforce users interact with a subset of JIRA Projects, for all these Projects the JIRA Integration user requires the following permissions:

Jira Permissions

Sinergify Feature

Comments

Browse Projects

  • Create Issue

  • Search Issues

  • Link Issues

  • View Issue Details

  • Sync Issue updates

Ability to browse projects and the issues within them.

Create Issues

  • Create issues

Permission to create issues and sub-tasks (if enabled) in the project.

Edit Issues

  • Edit Issue

  • Transition Issue

  • Create Issue (*JIRA Cloud)

  • Link Issue (*JIRA Cloud)

Ability to edit issues.

Delete Issues

  • Delete Issue

Sinergify only allows deletion of Issues created from Salesforce.

Linked Issues can not be deleted from Salesforce.

Transition Issues

  • Transition Issue workflow

Ability to transition issues.

Close Issues

  • Transition Issue to Closed status

Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.

Resolve Issues

  • Transition Issue to Resolved

Ability to resolve and reopen issues. This includes the ability to set a fix version.

Schedule Issues

  • Edit Issue

Ability to set Due Date Issue field. If not enabled the field Due Date is not displayed in the Create/Update Issue form in Salesforce.

Assignable User

  • Create Issue

  • Edit Issue

In the scenario where the Reporter/Creator of the Issue is configured also as the default Assignee.

Assign Issues

  • Create Issue

  • Edit Issue

Ability to Assign the Issue to JIRA users in create or edit issues. If disabled the field Assignee is not displayed in the Create/Update Issue form in Salesforce & Salesforce users might not be able to Create Jira.

Modify Reporter

  • Create Issue

  • Edit Issue

Ability to specify the Reporter. If disabled the field Reporter is not displayed in the Create/Update Issue form in Salesforce & Salesforce users might not be able to Create Jira.

View Voters and Watchers

  • Sync Issue updates

  • View Issue Details

If not enabled Salesforce can not pull Votes and Watchers Issue fields. Also these fields will not be displayed in the Jira Issue Details page within Salesforce.

Add Comments

  • Send comments to JIRA

Ability to add comments to the respective Jira Record within Salesforce.

Edit All Comments

  • Update comments

Ability to update comments already sent to Jira.

Edit Own Comments

  • Update comments

Ability to update comments already sent to Jira.

Create Attachments

  • Send Attachments to Jira

Users with this permission may create attachments.

Necessary Permissions for Jira Integration User for Team managed projects

For Team-Managed Projects, ensure the following considerations:

  • Project Roles: Team-Managed Projects use roles to assign permissions. The Jira Integration User should have a role with sufficient permissions (e.g., Viewer, Editor, or Admin).
  • Project-Specific Permissions: As Team-Managed Projects are independently managed, check that the Integration User is added to the specific project with the necessary permissions to browse, edit, and update issues.