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.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you want the issue type be part of the key, you could introduce your own "key" notion:
Bingo!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.