Let's say the name of my project in JIRA is XYZ
The default way JIRA assigns issue key numbers for this project is XYZ-1, XYZ-2 and so on.
I would like to customise this based on some other criteria. Is this possible? Like also adding a component name to the issue key?
One example of requirement for the format is <PROJECT>-<COMPONENT>-#.
So, XYZ-SERVER-1 is a custom format I'm looking for - is this possible?
Thanks in advance,
Hello @PWS Dev
I have implemented something similar to what you want.
First of all as @Dave Bosman _Realdolmen_ mentioned, it's not possible to modify issue key of an project and also it's not recommended as issue key is a combination of project key and a number.
If you want to append Component in your issue key like this
Then you should use the concept of "scripted fields" , I use the paid plugin Script runner for this.
When the issue screen loads the scripted field auto-calculates the custom issue key and is displayed as part of the scripted field, and the best part is that you can also query for scripted fields.
Hi @Tarun Sapra
I could be wrong here. But you would just create a new field this way and you do not modify the issuekey itself. So it's a workaround.
But it is a nice solution and will probably be the "next best thing" if someone would need something like a custom issue key.
Yes, for the approach I have suggested, it requires an creation of an scripted field. As out of the box it's not feasible to implement the original requirement, but since this kind of requirement is not uncommon hence the suggestion for an alternate.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events