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
4,365,998
Community Members
 
Community Events
168
Community Groups

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

1 vote
Answer accepted

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!

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

0 votes
Timothy Rising Star Feb 21, 2013

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events