Issue key in smart commit resolves to a crucible link

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

1 answer

1 votes

Hi Scott,

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

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

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,864 views 12 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot