Ok, I will go ahead and file an INFRA ticket to request this

Rob



On 5/29/13 3:14 AM, "Andy Seaborne" <[email protected]> wrote:

>+1
>
>Having the JIRA track a longer running set of changes is easier than
>digging up stuff in commits@
>
>       Andy
>
>On 29/05/The link seems to say swagger need to change, not ELDA.
>
>       Andy13 09:37, Ian Dickinson wrote:
>> +1 - I use this feature on our internal company source control system,
>> and, frankly, I only skim [email protected] because of the volume and
>> relative value compared to all of my other input streams :)
>>
>> Ian
>>
>
>
>> On 29/05/13 09:27, Claude Warren wrote:
>>> +1 for all the above reasons
>>>
>>>
>>> On Tue, May 28, 2013 at 11:16 PM, Stephen Allen <[email protected]>
>>> wrote:
>>>
>>>> I think this feature is useful.  I find it useful on my company's JIRA
>>>> system, and I always try to mention the JIRA number in my commit if
>>>> there is one.
>>>>
>>>> -Stephen
>>>>
>>>> On Tue, May 28, 2013 at 4:59 PM, Rob Vesse <[email protected]>
>>>>wrote:
>>>>> Some of the PMC probably already saw this on the Apache committers
>>>>>list
>>>> - http://www.apache.org/dev/svngit2jira.html
>>>>>
>>>>> This looks kind of useful, we have this a little bit already since
>>>>>the
>>>> build server will comment on JIRA issues if you mention an issue key
>>>> though
>>>> I think this may only happen if you've added new tests in your
>>>> commit(s)?
>>>>>
>>>>> Is it worth us requesting to have turn this on so issues will receive
>>>> continuous comments as commits mention them rather than only when an
>>>> appropriate build has succeeded?  I guess this depends on whether
>>>>others
>>>> are frequently including issue keys in commit messages and whether
>>>>they
>>>> find having the commit message duplicated to JIRA be valuable or not,
>>>> most
>>>> devs are probably reading the commit log or subscribed to the commits
>>>> list
>>>> but users reporting issues may not be and this may be a nice way for
>>>> them
>>>> to have more visibility that their issue is being worked on.
>>>>>
>>>>> Rob
>

Reply via email to