I'm bleary-eyed trying to find a solution to this that doesn't require some add-on or another.
I just want to prepend the issue number to the Case Summary of existing cases.
Example Case Summary for issue XYZ-123:
Before: "The thing doesn't work"
After: "[XYZ-123] The thing doesn't work"
I realize that if I use a string variable on a case that does not yet have an issue number that there will probably be an untranslated variable in the string until the issue is actually receives a number.
"[%issue.number%] The thing doesn't work"
I'm not a programmer by any stretch of the imagination, so hopefully there's something as simple as... say... the syntax of the [~username] function. BTW, [~issue.number] didn't work. :-)
Thank you in advance.
Storing information in more than once place is not a good idea in general. If you move the issue to another project then the issue key (XYZ-123) will change to ABC-123 and now your Summary field has outdated information. Also, removing such information from Summary fields once they have been changed is hard to automate.
All JIRA issues have issue keys but there's no way to insert something (e.g. wiki markup) that will later be replaced by the issue key.
If you really need to do this, you need to be ready for a bit of coding.
Author of Practical JIRA Administration, O'Reilly
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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