enable Development integration in JIra

[jtnord]

Service(s)

Jira

Summary

Please enable the Jira SCM developer integration
https://confluence.atlassian.com/jirasoftwareserver/configuring-development-tools-938845350.html

it is painful to have to link GitHub SCM commits PRs to Jenkins JIra issues when Jira can do all this automatically.

Additionally some people leave it as a comment, and others leave it as a web link meaning it is not always easy to find the information quickly.

By configuring the developer integration linking commits/PRs to jira tickets becaomes automatic, and you can even see in Jira if the commit is released or not.

If desired a workflow could then be implemented that could close (or mark the ticket as merged but unreleased) when a PR is merged, and / or in the future pick up a release so automatically mark the issue as closed when a tag is made containing the commit.

Reproduction steps

1. create a Jira issue
2. create a commit and PR where the title contains the Jira ID

Expected results

The development tab in JIra contains links to the commit and PR

Actual results

Nada

[dduportal]

Thanks @jtnord for raising this request. Seems a legit request (I can feel you) as it is (one the many) reason(s) why we moved the INFRA issue tracker to GitHub instead of JIRA (along with no efficient search, no discoverability, slow, painful UX, hard automation that requires a lot of expertise,e tc.).

Ping @olblak @daniel-beck @MarkEWaite @timja I need help from your memory: I might remember that we had an issue with the current JIRA distribution that we have at issues.jenkins-ci.org (hosted by the Linux Foundation) to integrate this plugin.

Something along the combination of "not atlassian cloud" and "SSO with our LDAP and not GitHub's".

Found some old issues but I can't strictly remember the reason (as I would like to re-evaluate it to see if we can enable it to help developers):

• [INFRA-323] Replace the SCM Jira Linker by the native DVCS plugin in Jira #300
• [INFRA-1507] Update JIRA linker bot to support the new JEP-3 workflow #1241

[daniel-beck]

IIRC we disabled this when it kept eating through the API limits.

[dduportal]

Looks like that there is a github app for that : https://github.com/atlassian/github-for-jira to benefit from api v4 (and no rate limit)

[jtnord]

Strange I thought it used events apart from the optional sync

[timja]

Looks like that there is a github app for that : atlassian/github-for-jira to benefit from api v4 (and no rate limit)

The app is useless for non cloud users:
https://github.com/atlassian/github-for-jira#requirements

It uses an OAuth token which has 5000 API requests per hour from what I remember.
You must set this up with a separate bot user not used for anything else as it will kill API limits otherwise.

It's also easy to accidentally use your own account when configuring it (this happened to my account at work).

The app is sometimes not that quick too because of rate limiting.

[dduportal]

Looks like that there is a github app for that : atlassian/github-for-jira to benefit from api v4 (and no rate limit)

The app is useless for non cloud users: https://github.com/atlassian/github-for-jira#requirements

It uses an OAuth token which has 5000 API requests per hour from what I remember. You must set this up with a separate bot user not used for anything else as it will kill API limits otherwise.

It's also easy to accidentally use your own account when configuring it (this happened to my account at work).

The app is sometimes not that quick too because of rate limiting.

Thanks for checking and sharing!

[daniel-beck]

You must set this up with a separate bot user not used for anything else as it will kill API limits otherwise.

Against GH ToS?

[timja]

You must set this up with a separate bot user not used for anything else as it will kill API limits otherwise.

Against GH ToS?

Not as far as I can tell. Each person on a free account is allowed one machine account.
https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#2-account-requirements

[dduportal]

Currently checking https://confluence.atlassian.com/adminjiraserver/integrating-with-development-tools-using-dvcs-1047552689.html