Is there a way to differentiate a Defect with D-XXXXX tags instead of IG-XXXXX

Roy July 23, 2021

Good morning and Happy Friday Team!

I wanted to ask a question here, in Jira all the tags shows as IG-XXXX for my project, irrespective of whether it is an Requirement, Defect, Epic. 

 Tags for Issues in JIRA.jpg

2 answers

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 23, 2021

Yes, that's correct, the key of an issue is the key of the project it is in and the sequence, separated by a hyphen.

To be clear - these are not "tags", they are the unique human identifier for an issue.

If you want to use a different identifier for the project part of it, you will need to move the issues into a different project, one with the key you want to use.

Roy July 23, 2021

Thanks Nic!

So, to be clear in Jira we do can't differentiate a Defect as D-XXXXX, a requirement as B-XXXXX, and Epic as E-XXXXX. All will show with the Project name which in our example is IG-XXXXX, irrespective of whether it is a Defect, or a Requirement or an Epic. 

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 23, 2021

Correct.

Unless you put the issue types into different projects.

I'm going to take a guess that you've been exposed to a legacy system that keys things like that.  It wasn't a bad idea 25 years ago, but nowadays, people have recognised that an indicator of responsibility is far more useful to imply in a key.  In Jira, the project instantly gives you an idea of the team to talk to, so Atlassian chose that (the issue type tells the end-user nothing they don't already know!)

0 votes
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 26, 2021

If you want the issue type be part of the key, you could introduce your own "key" notion:

  1. Create a read-only text type custom field called "My key"
  2. Then write a little script with ScriptRunner that initializes this field after the issue creation by:
    1. Taking the first character of the issue type ("B" for "Bug", "E" for "Epic", etc.)
      1. Alternatively you can define a mapping from issue type to the character (e.g. "Bug" -> "D")
    2. Taking the numerical ID of the issue (like 10003)
      1. Alternatively you can define a sequence but that may complicate things
    3. Concatenate the two and write to the field

Bingo!

Suggest an answer

Log in or Sign up to answer