JIRA Integration User Required Permissions

Oct 20, 2017 | Uncategorized

jira integration required permissions - featured image
In this page, we will describe all of the required  JIRA Integration User permissions.

JIRA Integration is not required to have Administrator privileges.

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

JIRA Permission zAgileConnect Feature Comments

Browse Projects
  • Link Issues
  • Create Issue
  • Search Issues
  • Sync Issue updates
  • View Issue Details

Edit Issues
  • Edit Issue
  • Transition Issue
  • Create Issue (*JIRA Cloud)
  • Link Issue (*JIRA Cloud)

Create Issues
  • Create Issue

Delete Issues
  • Delete Issue
 zAgileConnect only allows deletion of Issues created from Salesforce.

Linked Issues can not be deleted from Salesforce.

Transition Issues
  • Transition Issue workflow

Close Issues
  • Transition Issue to Closed status

Resolve Issues
  • Transition Issue to Resolved

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 issue. If not enabled the field Assignee is not displayed in the Create/Update Issue form in Salesforce.

Modify Reporter
  • Create Issue
  • Edit Issue
 Ability to specify the Reporter. If not enabled the field Reporter is not displayed in the Create/Update Issue form in Salesforce.

View Voters and Watchers
  • Sync Issue updates
  • View Issue Details
 If not enabled Salesforce can not pull Votes and Watchers Issue fields. Also theses fields will not be displayed in Issue Details VF page.

Add Comments
  • Send comments to JIRA
 Ability to send comments to JIRA with #salesforce.

Edit All Comments
  • Update comments
 Ability to update comment already sent to JIRA.

Edit Own Comments
  • Update comments
 Ability to update comment already sent to JIRA.

Create Attachments
  • Send Attachments to JIRA

User Masquerading (for JIRA Server Only)

Most of the zAgileConnect features are performed used the Integration user permissions. But certain operations like Create Issue, Update Issue, Transition Issue, etc can be performed using the current Salesforce corresponding JIRA User permissions (if Salesforce email address matches a JIRA user email address).

Tags:

Previous Post

Next Post

> You Might Also Like

How to Notify Salesforce Case Owner on Jira Issue Transitions

How to Notify Salesforce Case Owner on Jira Issue Transitions

Mar 26, 2018

The steps below describe the integration of Jira Issue updates to Salesforce via zAgileConnect with Salesforce Flow and Process Builder. The objective in this example is to notify Salesforce Case owner via email based on certain Issue Updates posted to Salesforce from...

Salesforce Expiring Certificate Notification (oauthjira)

Salesforce Expiring Certificate Notification (oauthjira)

Nov 9, 2017

Background Example of Salesforce Expiring Certificate Notification: You have one or more certificates in your Salesforce org <org ID> that will expire soon. Review the list below and visit Certificate and Key Management from Setup to make an update. - oauthjira,...

Loading...