This question is in reference to Atlassian Documentation: Administering JIRA Software
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
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..
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.
I have the similar requirement of Gennady Simkin i.e. customized key number based on the Project + Issue type.
PRO1_REQ_1 - requirements
PRO1_TC_1 - Test cases
PRO1_D_1 - For defects
Challenge is if I have ONLY the Project + number (example:- PRO1_1), does not give me the clear picture is it a requirement, test case, defect etc. when it is referred out of JIRA tool.
Do we have any updates made in JIRA to accommodate this request
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs