Smart commit on a merge is not processed

Question

Hello, According to the documentation, a smart commit for transition is: ISSUE_KEY # However, when I do a merge commit this does not work. The merge commit is of the form: Merge branch 'feature/itt-19' ITT-19 #implemented However, if I change the commit to: ITT-19 #implemented Merge branch 'feature/itt-19' Then it works. It also works with multiple lines commit messages as long as they don't start by merge branch.... Any idea on how to overcome this? We would like our merge messages to start by merge branch.... and still process the smart commits in them.

Andy Heinzer · Answer

Hi Albert,

Sorry to hear about this problem.  I understand that you are looking to use the smart commit here in order to transition an issue, but that this is not working as expected.  I did some research on the topic and found another support case where a user was having the exact same problem.

It appears to be due to a method in which the issue key is being evaluated.  And since that issue key appears in the branch name as well, in turn this is acting like a short-circuit of the intended way for this smart commit to work.  As you have noticed swapping the lines is a viable work-around for this problem, as the first line being processed will trigger Jira to transition correctly.

We currently have a public feature request that seeks to make this work the way you want over in JSWCLOUD-18886.  At the same time there is also an internal ticket that seeks to update our documentation to better reflect the usage/syntax state that exists today in Cloud.  On a side note you cited the Server version of the smart commits doc, I would expect an update to this over in the Cloud version of the same document soon.  Although right now that document is also not yet indicating of this limitation.

Sorry I do not have a better solution at this time, but I wanted to at least let you know that we are tracking this difference and seeking to clarify documentation as well.

Andy