Jira Cloud App Permissions
|Act as User||Required to get user specific details like the users time zone, and permissions.|
|Read||Required to check the existence of issue keys identified during synchronization of jobs and build and getting available configuration data for Automation Rule elements.|
|Write||Required to write build/deployment data for the Development Panel Integration and creating, updating or transitioning issues via Automation Rules.|
|Delete||Required to delete build/deployment data form the Development Panel Integration.|
|Project Admin||Required to create and update project versions from Automation Rules.|
Jenkins to Jira Path Access Permissions
Jenkins notifies Jira when a build in completed. It does this be accessing https://jjc.marvelution.com/rest/[tenant.id]/*
Data send to Jira depends on how the Jenkins site is registered in Jira.
- In case the site is registered as a public site, then its an empty trigger for Jira app to synchronize a newly completed build.
- In case the site is registered as a private site, then the trigger contains the data the Jira app needs to synchronize and index the build.
Jira to Jenkins Path Access Permissions
Below lists the paths that the Jira app will access in Jenkins.Traffic from the Jira cloud app is coming from Source IP 220.127.116.11, be sure to whitelist this IP address.
[GET] plugin/jenkins-jira-plugin/ping.html is used to check if the Jira Integration for Jenkins plug-in is installed on the Jenkins site.
[POST] plugin/jenkins-jira-plugin/register/ is used to register the Jira site with the Jenkins site.
[POST] plugin/jenkins-jira-plugin/unregister/ is used to unregister the Jira site with the Jenkins site, done when a site is deleted in Jira.
[GET] **/api/json/ is used to collect job and build data from Jenkins.
[POST] **/jji/build/ is used to trigger a new build of a job on Jenkins.
Previous: Use case: Transition issue when work starts