You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/09/07 23:18:20 UTC

[jira] [Assigned] (INFRA-12551) SVN hook to update Jiras with change sets stopped working 2 1/2 months ago

     [ https://issues.apache.org/jira/browse/INFRA-12551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambertus reassigned INFRA-12551:
---------------------------------------

    Assignee: Chris Lambertus

> SVN hook to update Jiras with change sets stopped working 2 1/2 months ago
> --------------------------------------------------------------------------
>
>                 Key: INFRA-12551
>                 URL: https://issues.apache.org/jira/browse/INFRA-12551
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA, Subversion
>            Reporter: Marshall Schor
>            Assignee: Chris Lambertus
>
> Our Jira (for the UIMA project) has been automatically associating SVN commits with Jira issues when the commit message contains the Jira issue near the start.  This stopped working about 2 1/2 months ago.  Looking at https://fisheye6.atlassian.com/browse/?sort=display_name&d=asc&page=3
> you can see this is true for many ASF projects besides ours (examples: tomcat, subversion itself).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)