You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Are there any naming conventions for JIRA labels? Trying to find a way to standardize on label usage.
JIRA labels observe the following conventions:
Suggested JIRA label conventions:
Thanks, @Nic Brough -Adaptavist-.
Lower case, alphanumeric or a hyphen (for separators), and of a restricted length.
The popular convention seems to be lower case with hyphenated compounds and snake case.
To help users out, I'd want a system that
Suggests similar labels to what they're typingThis is currently supported. Labels that have '/' or ':' do not show up as sugggestions. '-' and '_' are included in the suggestions.
Two layers - one predefined by administrators as "good" and then free-range on the restThis one is interesting. Could be an enhancement request in a later version of JIRA. Should it be color coded in the suggestions autocomplete renderer?
A spelling check to suggest better words (not enforce, just suggest)I wonder how this will work with the suggestions autocomplete renderer as the current function is based on existing labels.
Ref: JIRA v7.2.x
Hi - One frustration im finding is that Labels only return items that are in the same space - I work across 2 different Confluence spaces and use the same label for pages in BOTH spaces - but when i click a label in Space A, only pages in that space are shown on the list.
Is there any Cross-Space labelling that anyone knows about?
How can I return pages from >1 space with the same label? Many thanks as always! Adrian
But this question was more focused on JIRA I believe.
Boris - thankyou so much, thats exacty what I wanted and stupidly easy as well. Cheers.
I actually take a slightly different approach to this. I don't give people best practices because labels are not intuitive. There are a million other things that I would rather educate them on instead like how to write their own JQL.
My approach is twofold:
Whatever usage of labels I end up with is fairly small and not worth the effort to try and manage.
@Boris Berenberg - Atlas Authority,
Custom fields should be used where applicable. This however requires JIRA privileges.
Labels are free range and educating Jira users on effective JQL with labels will certainly help. This includes good choices for labels.
The usage of labels depends on the number of users, number of issues, number of JIRA projects and its related management. I see an increase in its usage as it does not need additional privileges.
Striking the right balance between free range and governance could be key.
We have 20K users on our JIRA instance and when I start typeing in the Labels field, ALL those labels appear. So, to simplify things we DID have to use repetitions with our labels.
We prefixed each label with something that was unique amongst all the labels in our JIRA installation. For example "SX_" then all the labels for our team began with "SX_". Then we went further into categories, so for example all labels relating to a region where prefixed with "SX_RGN_" ie: SX_RGN_Asia, SX_RGN_England... or a business line category was "SX_BL_" allowing labels like SX_BL_Equity, SX_BL_Debt. So when a user started typing a label and they entered the SX_ followed by the CAT_, they saw all the options available.
Why did we do this?
Just a tip for anyone that finds themselves in an environment like ours.
I am actually planning to update my existing labels to be like those you described. I'm curious if this has been effective for you? Have you encountered any issues? Anything you wish you knew ahead of time?
>"Single word: JIRA supports only single-word labels."
Okay, I have come across an unusual case where this is not the case.
I was needing to add to individual JIRA tickets and did this via a copy/paste from another document, rather than typing them in (there were a lot)
These are the methods:
So, yes, you can add a label with spaces!
A bug? You decide...
I really wish they'd undo that change and ban spaces in labels. Have a look at the community labels here - we had 20,000 of them when we started, with around 10,000 of them being utterly useless because of spaces.