[ 
https://issues.jenkins-ci.org/browse/JENKINS-13535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sogabe updated JENKINS-13535:
-----------------------------

    Component/s: jira
                     (was: github)

Which version of JIRA plugin do you use? 
GitHub plugin 1.2, JIRA Plugin 1.29 work fine.
                
> GitHub Commits with JIRA case ids surrounded by square brackets don't get 
> links in "Changes" section
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13535
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13535
>             Project: Jenkins
>          Issue Type: Bug
>          Components: jira
>    Affects Versions: current
>         Environment: Jenkins ver. 1.447.2-SNAPSHOT (private-04/12/2012 09:04 
> GMT-vjuranek). I don't have access to the actual machines running Jenkins, 
> but since this is actually Red Hat internal QA. It is safe to assume that it 
> is running on Red Hat Enterprise Linux a.k.a. RHEL.
>            Reporter: Francisco Borges
>            Priority: Minor
>         Attachments: NoChangesLinksWithLeadingSquareBracket.png
>
>
> I am a Red Hat HornetQ developer https://github.com/hornetq/hornetq some team 
> members write commits messages like this
> [JIRA-1234] Fixed something.
> Turns out that JIRA case id surrounded by square brackets will make the 
> commit to have no links nor commit description in the "Changes" section.
> FWIW, one actual such commit message is 
> "[HORNETQ-906] fix broken tests" taken from 
> https://github.com/hornetq/hornetq/commit/a4017b203ec097ec4fd2af9c27c3bad35426e667
>  
> See the attached screen shot for what happens with our "Changes" view.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to