Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Change Fisheye smart commit ISSUE_KEY detection


I’m searching an option so override the Fisheye smart commit ISSUE_KEY detection.

The background is that we use an own ticket number for our customer issues. We have added an own field with this ticket number to Jira already. We also have some crosslinks installed. The issue is that our developers has to commit under the ticket number, because additional processes are triggered in the background. So that we have to keep this ticket number in your system.

So we are searching for an option to modify the commit <-> Jira issue assignment.

Is there an option to override / extend the Fisheye smart commit ISSUE_KEY detection?

Or are we able to implement an own issue assignment?

We could just force our developer to add the ISSUE_KEY and the ticket number in each commit, but as you know this could end in chaos.

We would use the latest Jira and Fisheye version.
Our repo is SVN.

Thank you for your efforts.

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

196 views 1 6
Read article

Atlassian Community Events