Best practice for Crucible Project Keys

If I have a JIRA project with key FOO, what should I use for the Crucible project? At first I wanted to use the same key, but this gets in the way with smart commits. For this reason I decided to use some Postfix like FOOR. While this solves my problem with smart commits, it sure does not look nice. Does anyone have a better idea?

3 answers

1 accepted

This widget could not be displayed.

Hi Stefan.

According to Atlassian's best practises for Crucible configuration the suggested method is to use "CR-" prefix. So if you have "FOO" JIRA project then the Crucible project key should be "CR-FOO".

That's what I've been using in several different organizastions and haven't run into any problems or complains.

Cheers!

Thank you very much!

This widget could not be displayed.
Timothy Chin Community Champion Feb 21, 2013

If postfix is not nice, what about prefix? Kinda the same thing but yea..

This widget could not be displayed.

The problem with prepending 'CR-' is that you will hit this bug: https://jira.atlassian.com/browse/FE-4155

It
means that the smart commits see CR-FOO-xx and then associate the check-in with issue FOO-xx even though the check-in might be for issue FOO-yy

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

290 views 1 4
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