[Jenkins-infra] Automatically linking tickets between JENKINS and internal tracker

[R. Tyler Croy]

(replies inline)

On Thu, 30 Nov 2017, James Dumay wrote:

> Hi all,
> 
> I just wanted to ask permission before I did this, but when I am working in
> the community JIRA I often needing a way back to the mirror issue in the
> CloudBees private JIRA tracker. I spend a up to 10-15 hours a week in JIRA.
> 
> I'd like to setup a bot that automatically adds a backlink to our internal
> issue tracker from any JENKINS ticket. You can see an example of what this
> would look like below.
> 
> Any objections?


I don't particularly care, my only requests are:

* Make sure your bot doesn't spam the shit out of our JIRA
* Make sure that a random user who stumbles into the ticket understands what
  that link is and why they cannot access it. Simply "CD-123" is not clear to
  anybody outside of CloudBees.




- R. Tyler Croy

------------------------------------------------------
     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>
     xmpp: rtyler at jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20171129/f09f6299/attachment.asc>