nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project key with numbers

unknown

Is there any known issues for project keys with numbers?

We thinking about changing 'jira.projectkey.patter' parameter to allow numbers, but afraid that something can go wrong with these keys (as within JIRA itself, as well and with Confluence / Fisheye links).

Accepted answers

Nic Brough -Adaptavist-

They can break some addons (notably Agile), and changes to the key are not supported by Atlassian.

However, the break of addons only seems to happen when you use a number as the first letter of a key, and Jira 6.1 does improve support for changes of key. Although it's not an explicit recommendation by Atlassian, the general advice is to keep the first character of the key as A-Z, then you can use A-Z, 0-9 and underscores for the rest of it (minimum length 2 characters as well)

All comments

Nic Brough -Adaptavist-

They can break some addons (notably Agile), and changes to the key are not supported by Atlassian.

unknown

I'm sorry, but what exactly doesn't supported by Atlassian? Bugs related to project keys with numbers?

HenriqueA

Hi Aliaksei,

It's not a problem to use numbers on key format.

I just recommend that you use the supported format. Here is what the official documentation says:

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:

Examples of supported keys: PRODUCT_2013, R2D2, MY_EXAMPLE_PROJECT.

Examples of unsupported keys: 2013PROJECT (first character is not a letter), PRODUCT-2012 (hyphens are not supported).

If you want to see the complete documentation, here is the link: https://confluence.atlassian.com/display/JIRA/Changing+the+Project+Key+Format

Cheers,

Nic Brough -Adaptavist-

Changing the project key to something outside an Atlassian recommended format is not supported.

They'll code on the assumption that you don't go outside a recommended format, so there's a small chance that they might even add new problems inadvertently.

In other words, if you do it, and you have a problem which needs support, then Atlassian are entitled to say that they aren't going to try to help you, at least until you go back to a supported format. (In real life, they'll really do their best to help you without demanding changes like that)

Rahul Aich [Nagra]

@Nic: I would not recommend having an underscore as my project key. It is a known issue on jira 5.0-jira5.2.5 that activity stream does not work if project key has underscore. Fixed in 5.2.5 though.

Rahul

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration