You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Andy Kurth (JIRA)" <ji...@apache.org> on 2013/09/24 19:52:05 UTC
[jira] [Created] (INFRA-6785) svngit2jira for VCL
Andy Kurth created INFRA-6785:
---------------------------------
Summary: svngit2jira for VCL
Key: INFRA-6785
URL: https://issues.apache.org/jira/browse/INFRA-6785
Project: Infrastructure
Issue Type: Task
Reporter: Andy Kurth
Thank you very much for creating svngit2jira!
Which project is interested in this service: VCL
Is the project in agreement on using this? Yes, see http://markmail.org/thread/imzmz5szvkxdkgqs
What JIRA name does your project use? VCL
Do you use git or subversion: subversion
How would you like commits to trigger an update of a JIRA ticket:
Any commit message containing VCL-xxx on its own line should trigger a commit. Commit messages may contain multiple sections which correspond to different Jira issues. The sections are split up by the VCL-xxx lines, or possibly the word "Other":
{noformat}
VCL-123
Updated foo
VCL-456
Updated bar
yadda
Other
Fixed typo
{noformat}
This example would add "Updated foo" to VCL-123 and "Updated bar...yadda" to VCL-456. "Fixed typo" would not be added to any issue. I'd greatly prefer if it didn't add the entire message to both Jira issues, only the section up to the next VCL-xxx or Other line.
It would be handy if the same commit text could be added to multiple Jira issues if the following syntax is used:
{noformat}
VCL-123 VCL-456
Added blah subroutine used by foo and bar
VCL-789
Added gizmo
{noformat}
This example would add "Added blah" to VCL-123 and VCL-456, and "Added gizmo" to VCL-789.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira