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
Next: Root
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.
So I have a group that has a 200+ projects a year. These are not phases, they are each unique projects.
* They have latched on to the PROJECT KEY being a way to help them distinguish projects.
*I looked into it, and saw the information below, but then when I tried t his on cloud, I seemed to have a limit of 10 not 20.
*What are the limitations of the PROJECT KEY in JIRA Cloud? I cannot seem to find it spelled out like below.
*Are we approaching this wrong, and what them not get hung up on the project key?
*I did encourage them to think of good project names, but I think its because when they open a ticket they see ABC-123 they want the "ABC" to make sense.
Any help/thoughts/guidance appreciated :)
Regarding Project Key; information found here (https://confluence.atlassian.com/adminjiraserver/changing-the-project-key-format-938847081.html)
PRODUCT_2013
, R2D2
, MY_EXAMPLE_PROJECT
. 2013PROJECT
(first character is not a letter), PRODUCT-2012
(hyphens are not supported).
The default key size is set to 10. You can have this changed by your Jira administer. As for the supported formats, in my version of Jira Cloud, I cannot use hyphens or underscores.
I get the error "Project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters." after having a project key start with "Agile".
Adding to this, the length specification for Project Key is documented here:
https://support.atlassian.com/jira-cloud-administration/docs/configure-jira-application-options/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks so much @Nolan Mcconnell & @Trudy Claspill
I am a JIRA Admin, so maybe I can look into this. But I also understand the risk of doing this so will be careful and think through before making these changes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.