Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47990

Allow custom regular expression for finding JIRA issues in commit messages

    Details

    • Similar Issues:

      Description

      Our Devs changed the way they write commit messages and are taking the following approach https://chris.beams.io/posts/git-commit/It differs in one way: Instead of referencing other commits they write JIRA issue keys in the body. For example
       
      Commit subject
       
      Commit description
      See: TICKET-1234
      Resolves: TICKET-456, TICKET-789

      Therefore we cannot use the Jira-Ext Plugin anymore, because commit messages don't start with the issue key and switching to "Mentioned somewhere in the commit message" would also trigger referenced issues under "See" that aren't resolved.

      I would be nice if you could add an option "Regular Expression" which allows to define a custom regular expression for finding (multiple) issue keys in a commit message. This would solve our situation, and would probably cover all future requests from other users, which a similar problem.

        Attachments

          Activity

          flaimo flaimo flaimo created issue -
          flaimo flaimo flaimo made changes -
          Field Original Value New Value
          Description Our Devs changed the way they write commit messages and are taking the following approach [https://chris.beams.io/posts/git-commit/]It differs in one way: Instead of referencing other commits they write JIRA issue keys in the body. For example
           
          {color:#990000}_Commit subject_{color}
          {color:#990000} {color}
          {color:#990000}_Commit description_
          {color}
          {color:#990000} {color}{color:#990000}_See: TICKET-1234_
          {color}{color:#990000}_Resolves: TICKET-456, TICKET-789_{color}

          Therefore we cannot use the Jira-Ext Plugin anymore, because commit messages don't start with the issue key and switching to "Mentioned somewhere in the commit message" would also trigger referenced issues under "See" that aren't resolved.


          I would be nice if you could add an option "Regular Expression" which allows to define a custom regular expression for finding (multiple) issue keys in a commit message. This would solve our situation, and would probably cover all future requests from other users, which a similar problem.
          Our Devs changed the way they write commit messages and are taking the following approach [https://chris.beams.io/posts/git-commit/]It differs in one way: Instead of referencing other commits they write JIRA issue keys in the body. For example
            
           {color:#990000}_Commit subject_{color}
           {color:#990000} {color}
           {color:#990000}_Commit description_{color}
          {color:#990000}_See: TICKET-1234_
          _Resolves: TICKET-456, TICKET-789_{color}

          Therefore we cannot use the Jira-Ext Plugin anymore, because commit messages don't start with the issue key and switching to "Mentioned somewhere in the commit message" would also trigger referenced issues under "See" that aren't resolved.

          I would be nice if you could add an option "Regular Expression" which allows to define a custom regular expression for finding (multiple) issue keys in a commit message. This would solve our situation, and would probably cover all future requests from other users, which a similar problem.

            People

            • Assignee:
              dalvizu Dan Alvizu
              Reporter:
              flaimo flaimo flaimo
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: