Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

Custom Project Key and Project Key Limitations

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 (

  • regarding the project key 
  • It is recommended that the key be as short as possible. It is not supposed to be descriptive, but rather recognizable and unique. The name and theme of the project can change over time. If the key is too well defined, it will point to the past and not the present.
  • Ensure that you choose a supported project key format. Only formats that meet all of the following rules are supported:
    • The first character must be a letter,
    • All letters used in the project key must be from the Modern Roman Alphabet and upper case, and
    • Only letters, numbers or the underscore character can be used.
      • Examples of supported keys: PRODUCT_2013R2D2MY_EXAMPLE_PROJECT.  
      • Examples of unsupported keys: 2013PROJECT (first character is not a letter)PRODUCT-2012 (hyphens are not supported).


1 answer

1 accepted

1 vote
Answer accepted

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". 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 21, 2023

Adding to this, the length specification for Project Key is documented here:

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. 

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events