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

Richard Bywater richard at byh2o.com
Thu Nov 30 03:49:16 UTC 2017


Fair enough - I'm guessing that it would only really be used in Cloudbees
driven components like BlueOcean anyway so wouldn't be widespread?

Richard.

On Thu, 30 Nov 2017, 4:41 PM James Dumay, <jdumay at cloudbees.com> wrote:

> Yes, there are private discussions going on in those private tickets that
> involve commercially sensitive information from CloudBees customers. For
> full transparency, those discussions are going to happen regardless if
> there is a link or not.
>
> Typically we make an effort to summarize the problem on the public ticker
> with the confidential information redacted. That means any work that we
> schedule for Jenkins ends up with a public ticket where the community is
> able to collaborate on those items as contributors see fit.
>
> This link helps the dozens of people who are triaging the Jenkins issue
> tracker at CloudBees and who are actively making cases to put management to
> invest more in OSS improvements.
>
> Put another way, I’d rather us be doing less administrivia and more work
> on improving Jenkins.
>
>
> On Thu, 30 Nov 2017 at 2:28 pm, Richard Bywater <richard at byh2o.com> wrote:
>
>> Personally I'm a little -1 on this (-0.5 perhaps? :) ) but only because
>> it frustrates me when there is a public ticket that links off in some way
>> to a place that isn't accessible. Kind of makes you think there is some
>> hidden discussions happening in the private tracker.
>>
>> Richard.
>>
>> On Thu, 30 Nov 2017, 3:51 PM James Dumay, <jdumay at cloudbees.com> 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?
>>>
>>>
>>> [image: Screen Shot 2017-11-30 at 1.23.29 pm.png]
>>> --
>>> James Dumay,
>>> Director of Product Management.
>>> CloudBees, Inc.
>>> Skype: jdumaycb Twitter: i386
>>> Meet with me: https://calendly.com/jdumay
>>>
>> _______________________________________________
>>> Jenkins-infra mailing list
>>> Jenkins-infra at lists.jenkins-ci.org
>>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>>
>> --
> James Dumay,
> Director of Product Management.
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
> Meet with me: https://calendly.com/jdumay
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20171130/14ef29f9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-11-30 at 1.23.29 pm.png
Type: image/png
Size: 45783 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20171130/14ef29f9/attachment-0001.png>


More information about the Jenkins-infra mailing list