Worst Jira Admin Contest: Sesquipedalian Project Names

[#1]

Mistake 13

Ses·​qui·​pe·​da·​lian - having many syllables, characterized by the use of long words

How long should a Jira project key be? While a long key is allowed in Jira, it makes little sense to make end users type something too long.

Jira project names and project keys are critical attributes to help identify projects and issues.  A best practice is to make the project's title similar to the project key. Users should be able to communicate using either project name.

• Example long name: Development

• Example key: DEV

Project names should be descriptive yet generic. Example: A project with the key "ACME“ doesn't tell the user what kind of issues should be reported in that location.

Also, avoid numbers in project names. Project keys like ACME2024 means you’ll have issues IDs formatted like ACME2024-25. This is both confusing and unnecessary!

The project key, and other Jira settings (like statuses and custom field names), should be short in length where possible.

---

Back to intro and mistakes list

[Bill Sheboy]

Yes, and...

Going too far the other direction could be problematic as well.  When one needs to find the company's official "Keyword, Acronym, and Acrostic Generator v3.4.1" to know what a project is about, that seems like a smell of other root causes.