JIRA/Fisheye Smart Commit Workflow Changes

[John French]

So we are using (or attempting to use) Smart Commits in Subversion with JIRA/Fisheye.  Successful smart commits generally follow the same syntax of the corresponding JIRA action such as #comment, #developer-accepts, #close, #resolve, etc.  The command #start-work also works as a smart commit; however, in our instance of JIRA- you cannot start work on a ticket without selecting a Fix Version for that ticket.  I am wondering if there is a command to add after #start-work so JIRA can assign the fix version to that ticket and accept the smart commit?

The error message we get from Fisheye is "FishEye was unable to execute the transition "Start-Work" on the issue XX-123 because JIRA responded with the following error: fixVersions: Fix Version/s is required.

Thanks for any help!

[GabrielleJ]

It's a tool limitation that is defined in the documentation:

Note that:

• Smart Commits only support the default JIRA Software issue key format (that is, two or more uppercase letters, followed by a hyphen and the issue number, for example BAM-123).
• Smart Commits don't provide for field-level updates in JIRA Software issues.

• When using Smart Commits you can use linkers that create a hyperlink to the JIRA Software issue. See Linkers for more information.

• If there are any errors during the processing of Smart Commits, they will be logged to FishEye's error console, as well as emailed to the actioning users. Speak to your FishEye administrator about Configuring SMTP.

Reference: https://confluence.atlassian.com/fisheye/using-smart-commits-298976812.html#UsingSmartCommits-multiline

[John French]

Understood, so is there a way to remove the requirement to assign a Fix Version when transitioning a ticket to "Start Work"?  It seems weird that smart commits would be created for transitioning workflow statuses when most status changes require some other input/selection that smart commits cannot produce.  Thanks.

[GabrielleJ]

Yes, you can update your JIRA workflow condition/validator for the Fix Version.

[John French]

Thank you, removing the requirement to assign a fix version allows us to use smart commits to change the workflow status.  But now I'm wondering- is there a way to set up a hook within JIRA to edit an issue based on some command placed directly into the JIRA issue comment?  That way we could use the smart commit to change the workflow status, use the #comment command to place some text into the JIRA issue comment, then JIRA would take action (such as assign fix version, assign tester, etc.) based on that comment.  Would that be possible?

[GabrielleJ]

Fisheye does not have anything like that now. You can always open up a suggestion against Atlassian  support.atlassian.com