nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best practice for Crucible Project Keys

Stefan Egli

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?

Accepted answers

Grzegorz Dlugos

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!

All comments

Timothy

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

Grzegorz Dlugos

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!

Stefan Egli

Thank you very much!

pslootweg

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