Is it possible to specify issue name after #comment while using smart commits ?
( for example, EPMCESACF-18 #time 1d #comment EPMCESACF-18 fixed )
Because we have the error:
Error processing EPMCESACF-18 #comment
FishEye was unable to comment on the issue EPMCESACF-18 because JIRA responded with the following error: comment: Comment body can not be empty!
the commit message parser is able to match commands for multiple issues in the same commit message. So ehwn it finds 'EPMCESACF-18' after '#comment' it sees that as a separate command and doesn't find any text for the #comment command.
I've raised a bug for it that's tracked here: https://jira.atlassian.com/browse/FE-5024
As a workaround you can try avoiding using the issue key again in the comment (something like 'EPMCESACF-18 #comment fixed' should work ok)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs