Jira Cloud App Permissions
|Act as User||Required to get user specific details like the time zone.|
|Read||Required to check the existence of issue keys identified during synchronization of jobs and build.|
|Write||Required to write build/deployment data for the Development Panel Integration.|
|Delete||Required to delete build/deployment data form the Development Panel Integration.|
Path Access Requirements
|Path||Direction||Jenkins Site Scope||Reason|
|Jenkins to Jira||Public|
Used to push a notification to Jira to synchronize a newly completed build.
Used to push Job and Build data to Jira whenever a build completes or a job is created, modified or deleted.
|Jira to Jenkins||Public||Used to check if the Jira Integration for Jenkins add-on is installed on the Jenkins site.|
|Jira to Jenkins||Public||Used to register the Jira site with the Jenkins site.|
|Jira to Jenkins||Public||Used to unregister the Jira site with the Jenkins site, done when a site is deleted in Jira.|
|Jira to Jenkins||Public||Used to collect job and build data from Jenkins.|
|Jira to Jenkins||Public||Used to trigger a new build of a job on Jenkins.|
There are permission requirements that need to be setup correctly before the integration can work.
|Administrator||Global||Required for configuring the Jenkins sites, and selected what should be synchronized.|
|View Development Tools||Project||Required for users to view the Jenkins build date in Jira.|
Jenkins Integration User
These permissions are only needed for Jenkins Sites that are configured as public, where Jira can interact with Jenkins to post and collect data. No Special permissions are needed when configured a Jenkins site as private.
|Administer||Global||Required, only if the Jenkins plugin is installed, to be able to view Jenkins and to let Jira sites register themselves with Jenkins, see Jira Build Notification Listener|
|Read||Global||Required to synchronize the top level jobs.|
|Read||Job||Required to synchronize jobs and there builds.|
|Build||Job||Required for triggering builds from Jira.|
The Job permissions must be set on each Job