What are best practices we can follow for project naming and prefix for the issue keys

[sachin_salunkhe]

Hi Guys,

Please provide the details on how we can create the naming conventions for the new projects and the issue keys of the projects.

Also if you add the standards of JSM as an practice.

Thanks

Sachin

[Shawn Doyle - ReleaseTEAM]

Ah..the whimsical notion of 'best practice' makes me chuckle, that there's a 'Goldilocks' way of doing things - not too hot, not too cold, but just right.. What is best for one is often terrible for the next.

Pretty much, keep it simple, the KISS method.  Name the projects short and sweet enough that they resonate with the users yet they are unique enough to not step on each other and cause confusion.

[Joseph Chung Yin]

@sachin_salunkhe -

Hi Sachin:

Here is the common recommendation on project name and project key -

Project name - Keep concise and to the point, so when users see the name, it will convey the meaning for the project.  However, keep it short (Three or Four words will be the best)

Project key - Although it can be between 2 to 255 characters long.  The default is always set to 10 characters long.  Avoid using number character in the project key.  The shorter the key is, it is the best choice.

Here is a link on project configurations option guideline - https://support.atlassian.com/jira-cloud-administration/docs/configure-jira-application-options/

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.