You will need to write a custom solution for this where your solution generates a random id each time in 2 phases
As for specifics on how to write this, I do not have one offhand but hope the steps above help.
My question though is why don’t you want to use the default JIRA provided id?
The IDs for the stories and the tasks are currently the same for my project. LRE for stories and LRE for tasks associated with stories, the only difference is the associated ICON but I would like the custom ID (LRE) to be different for tasks, something like TAS or something....
I am not sure how to write custom solutions in JIRA, but Google here I come!!!
Why? What problem are you trying to solve?
I ask because a second key is pretty much useless to you. If you do it in text, you can't usefully report on it. It won't be a key for the issue, just a number or string that happens to be on it. You can't using for linking, inside Jira or externally.
I can't think of a good reason to create something that non-functional.
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