Overview

This page describes best practice for setting up the user permissions for:

• Users who are specified in partnership configurations in terms of minimum required permissions for the users used as Source and Destination Credentials for Partnership
• Users who are logged into JIRA when creating/linking issues via Herzum Quick Linker.

Introduction

A user logged into JIRA with browse permission on a given Project is allowed to view Herzum Quick Actions and Herzum Quick Links Panels but the allowed actions depends on:

• logged user grants
• user's grants set for Partnership Destination Credential
• user's grants set for Partnership Source Credential
• partnership main definition (Local or Remote)

Herzum Quick Linker allowed actions can be grouped into the four main categories below:

• issue creation and linking via Quick button (Create)
• issue creation and linking via escalate post function (Escalate)
• linking an existing issue (Link)
• data syncing (Sync).

The actions listed above are also allowed/restricted by the following conditions:

• For a local Partnership, issue creation via a Quick button or escalation via a post function depends upon the user credentials of the logged in user.
• For a remote Partnership, issue creation via a Quick button or escalation via a post function depends upon the destination credentials of the partnership.
• Issue linking depends upon the logged in user credentials for a Local Partnership and on the partnership’s destination credentials when a partnership is remote
• Syncing is dependent on the partnership’s source and destination credentials for both Local and Remote partnerships.

The table shown below provides a summarized view of the dependency between allowed actions and the provided users permission in the case of Local and Remote Partnership:

	Local Partnership				Remote Partnership
	Create	Escalate	Link	Sync	Create	Escalate	Link	Sync
Logged in User
Destination Credential
Source Credential

This guide provides details, for each scenario listed above, the required permissions for the logged in user and for the users set as Source and Destination Credentials for a Partnership.

Notice that if the required permissions are not granted the action is not allowed and an Alert is returned explaining which permission is missing. 

Issue creation and linking via Quick button in the case of a Local Partnership

The required permissions depends on the Issue Link type configured on the Mapping as shown below: 

• Issue Link type is Quick Link: logged in user must have Create issue permission on the Target Project.
• Issue Link type is JIRA Link: logged in user must have Create issue and Link Issues permissions on the Target Project.
• Issue Link type is Both: logged in user must have Create issue and Link Issues permissions on the Target Project.

Issue creation and linking via Quick button in the case of a Remote Partnership

User configured as partnership's destination credential must have Create issue permission on the Target Project.

Issue creation and linking via Escalate Issue post function in the case of a Local Partnership

Same project permissions required as for issue creation and linking  via Quick button case of a Local Partnership.

Issue creation and linking via Escalate Issue post function in the case of a Remote Partnership

Same Project permissions required as for Issue creation and linking  via Quick button case of a Remote Partnership.

Issues linking via Quick button in the case of a Local Partnership

The required permissions depend by the Issue Link type configured on the Mapping as shown below: 

• Issue Link type is Quick Link: logged in user must have Browse issue permission on the Target Project.
• Issue Link type is JIRA Link: logged in user must have Browse issue and Link Issues permissions on the Target Project.
• Issue Link type is Both: logged in user must have Browse issue and Link Issues permissions on the Target Project.

Issues linking via Quick button in the case of a Remote Partnership

User configured as partnership's  destination credential must have Browse issue permission on the Target Project.

Issues syncing for Comments in the case of a Local Partnership

The required permissions depend by syncing versus configured on the Mapping as shown below: 

• versus is bidirectional <=> :
  • user configured as partnership's source credential must have Add comment, Delete Own Comments, Edit Own Comments permissions on the source project
  • user configured as partnership's destination credential must have Add comment, Delete Own Comments, Edit Own Comments permissions on the target project
• versus is from source to target =>:
  • user configured as partnership's destination credential must have Add comment, Delete Own Comments, Edit Own Comments permissions on the target project
    
• versus is from target to source <= 
  • user configured as partnership's source credential must have Add comment, Delete Own Comments, Edit Own Comments permissions on the source project.

Issues syncing for Comments in the case of a Remote Partnership

Same project permissions required as for Local Partnership.

Issues syncing for Attachments in the case of a Local Partnership

The required permissions depend by syncing versus configured on the Mapping as shown below: 

• versus is bidirectional <=> :
  • user configured as partnership's source credential must have Create Attachment permission on the source project
  • user configured as partnership's destination credential must have Create Attachment permission  on the target project
• versus is from source to target =>:
  • user configured as partnership's destination credential must have Create Attachment permission on the target project
• versus is from target to source <= 
  • user configured as partnership's source credential must have Create Attachment permission on the source project.

Issues syncing for Attachments in the case of a Remote Partnership

The required permissions depend by syncing versus configured on the Mapping as shown below: 

• versus is bidirectional <=> :
  • user configured as partnership's source credential must have Create Attachment and Browse issue permissions on the source project
  • user configured as partnership's destination credential must have Create Attachment and Browse issue permission on the target project
• versus is from source to target =>:
  • user configured as partnership's destination credential must have Create Attachment permission on the target project 
  • user configured as partnership's source credential must have Browse issue permission on the source project
• versus is from target to source <= 
  • user configured as partnership's source credential must have Create Attachment permission on the source project 
  • user configured as partnership's destination credential must have Browse issue permission on the target project.

Issues syncing for Affect Version, custom fields, Summary, Description in the case of a Local Partnership

The required permissions depend by syncing versus configured on the Mapping as shown below: 

• versus is bidirectional <=> :
  • user configured as partnership's source credential must have Edit Issue permission on the source project
  • user configured as partnership's destination credential must have  Edit Issue permission  on the target project
• versus is from source to target =>:
  • user configured as partnership's destination credential must have Edit Issue permission on the target project
• versus is from target to source <= 
  • user configured as partnership's source credential must have Edit Issue permission on the source project.

Issues syncing for Affect Version, custom fields, Summary, Description in the case of a Remote Partnership

Same Project permissions required as for Local Partnership.

Issues syncing for Fix version in the case of a Local Partnership

The required permissions depend by syncing versus configured on the Mapping as shown below: 

• versus is bidirectional <=> :
  • user configured as partnership's source credential must have Edit Issue and Resolve Issues permissions on the source project
  • user configured as partnership's destination credential must have Edit Issue and Resolve Issues permissions  on the target project
• versus is from source to target =>:
  • user configured as partnership's destination credential must have Edit Issue and Resolve Issues permissions on the target project
• versus is from target to source <= 
  • user configured as partnership's source credential must have Edit Issue and Resolve Issues permissions on the source project.

Issues syncing for Fix version case of a Remote Partnership

Same project permissions required as for Local Partnership.

Issues syncing for Assignee in the case of a Local Partnership

The required permissions depend by syncing versus configured on the Mapping as shown below: 

• versus is bidirectional <=> :
  • user configured as partnership's source credential must have Edit Issue and Assign Issues permissions on the source project
  • user configured as partnership's  destination credential must have Edit Issue and Assign Issues permissions  on the target project
• versus is from source to target =>:
  • user configured as partnership's  destination credential must have Edit Issue and Assign Issues permissions on the target project
• versus is from target to source <= 
  • user configured as partnership's source credential must have Edit Issue and Assign Issues permissions on the source project.

Issues syncing for Assignee in the case of a Remote Partnership

Same Project permissions required as for Local Partnership.

Issues syncing for Reporter in the case of a Local Partnership

The required permissions depend by syncing versus configured on the Mapping as shown below: 

• versus is bidirectional <=> :
  • user configured as partnership's source credential must have Edit Issue and Modify Reporter permissions on the source project
  • user configured as partnership's  destination credential must have Edit Issue and Modify Reporter permissions  on the target project
• versus is from source to target =>:
  • user configured as partnership's  destination credential must have Edit Issue and Modify Reporter permissions on the target project
• versus is from target to source <= 
  • user configured as partnership's source credential must have Edit Issue and Modify Reporter permissions on the source project.

Issues syncing for Reporter in the case of a Remote Partnership

Same Project permissions required as for Local Partnership.