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; } } }

Jira issue types prefix

unknown

This question is in reference to Atlassian Documentation: Administering JIRA Software

Good morning.

Is there any way to configure various Jira issue types to generate issue types prefixes depending on the issue type created

For example if I have a BUG or custom item type such as Test Case or Requirement

Item number would look something like that BUG - 123, or for Requirement: REQ -123, or for Test Case: TC-123

Since by default all issue types use prefix from project names and not from issue types

Any help much appreciate it

Accepted answers

Jeff Louwerse

Other than what Nic mentioned with a project for each issue type, If you really wanted to you could create a new custom field, or a scripted field and create your own key like field.. however there really is no point to either of those options. It seems like a lot of overhead managing it all when can have one project and you can parse out the different types with a simple search criteria..

All comments

Nic Brough -Adaptavist-

The only way to do that is to put each issue type into its own project.

An issue key is always <project key>-<number>

unknown

Nope, you cannot change it to something like that. JIRA will always use the pattern globally configured, in this case the JIRA Project key. Besides, doing what you want will confuse everyone else like what project is REQ-123 for?

unknown

I would prefer to configure in such as way that the user would able to see a project name with an issue type all together for example

testproject/req-123

testproject/bug-123

testproject/ts-123

unknown

Your JIRA Project key can only be configured for a pattern (e.g. alphabets only, alphanumeric), but no ability add another variable on it.

Jeff Louwerse

Nic Brough -Adaptavist-

It can't be changed - you'd have to rewrite half of JIRA and a lot of the add-ons. I think Gabrielle is correct about the confusion as well. But also, you've already got the issue type as a field almost anywhere, so I can't actually see that this structure would add anything of use for the users. I know an issue is a bug by looking at the icon or text next to it.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software-cloud

jira-cloud

jira-core

issue-type