Issue key in smart commit resolves to a crucible link

Question

This question is in reference to Atlassian Documentation: Using Smart Commits

Normally developers check in source with comment like:

JIRA-100 text comments...

and when this entire line appears in the source tab, the JIRA-100 portion is a hyperlink to that JIRA-100 issue. However, some projects end up having the JIRA-100 hyperlinked to Crucible (where such review key does not exist) and gets a Crucible page with message "review not found"

Are there project linkage mis-configuration that would cause this?

Fisheye/Crucible 2.10.0, JIRA 5.2.8

thanks,

Scott

Scott Chang1 · Answer

We did have same project key between JIRA and crucible before but I had since changed the crucible project key to JIRA-CRU and the problem persisted

Piotr Swiecicki · Answer

Hi Scott,

Is this possible that you have a Crucible project of "JIRA" key configured in your system?