You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <ga...@gmail.com> on 2011/10/04 22:36:36 UTC

[ALL] Tip for commit comments matching JIRA tickets.

Hi All:

If you include the JIRA [issue] in your commit comment, for example
"[IO-284] super duper", you will see it in JIRA under the tab "Subversion
Commits".

For example:
https://issues.apache.org/jira/browse/IO-284?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel#issue-tabs

This is a super duper feature.

-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [ALL] Tip for commit comments matching JIRA tickets.

Posted by Simone Tripodi <si...@apache.org>.
Very nice! I used to add the issue key in the ci comment[1], but
didn't notice the activity on Jira before you notified :P
For OGNL, we have also the JenkinCI JIRA plugin that, based on getting
the issue id between [] in the ci message, adds a comment to the
issue, notifying in wich build the commit is integrated.
Thanks!
Simo

[1] https://issues.apache.org/jira/browse/CHAIN-60

http://people.apache.org/~simonetripodi/
http://www.99soft.org/



On Tue, Oct 4, 2011 at 10:36 PM, Gary Gregory <ga...@gmail.com> wrote:
> Hi All:
>
> If you include the JIRA [issue] in your commit comment, for example
> "[IO-284] super duper", you will see it in JIRA under the tab "Subversion
> Commits".
>
> For example:
> https://issues.apache.org/jira/browse/IO-284?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel#issue-tabs
>
> This is a super duper feature.
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] Tip for commit comments matching JIRA tickets.

Posted by sebb <se...@gmail.com>.
On 4 October 2011 21:36, Gary Gregory <ga...@gmail.com> wrote:
> Hi All:
>
> If you include the JIRA [issue] in your commit comment, for example
> "[IO-284] super duper", you will see it in JIRA under the tab "Subversion
> Commits".

AFAIK, the [] are not needed, just XYZ-123 will do.

> For example:
> https://issues.apache.org/jira/browse/IO-284?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel#issue-tabs
>
> This is a super duper feature.

Mostly...

However if you refer to a jira issue in another project, e.g. "IO-157
- Updated dependency on XYZ to avoid XYZ-123" that will also add a
comment to the XYZ JIRA (assuming it is an ASF JIRA). Sometimes that
may be useful; mostly it is probably just a nuisance for the other
project.

> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org