Is there a way to keep issues summaries in sync after renaming one of them?

Question

For JQL Query purposes, we have setup a naming convention that follows:

[Epic Summary (Project Name)] - [Issue Summary(Task Name)] - [Subtask Summary(Task Construction)]

The problem is if anyone changes the summary at any level, the parent(s)/children do not reflect that summary. In response to this we have made recursion transitions, which if used properly, will keep the naming convention in check. That said, there are many issues that were created before this naming convention was developed and it would take a lot of work to correct them all.

Is there a way in Jira, Scriptrunner, or other addons, to do mass renaming of a Epic and their Children?

Was hoping for something like:

[Enter name of Epic]
Change Epic Summary to: (Enter Summary)
-- Change Children Issues to Epic Summary - Issue Summary
-- Change Sub-Task Issues to Epic Summary - Issue Summary - Subtask Summary.

Thank you for your time!

Nic Brough -Adaptavist- · Answer

I'd approach the problem differently.  Rather than botch a potentially variable summary field which is usually more useful when filled with a proper summary, provide a scripted field to search on.

A ScriptRunner Scripted field that adds up the strings you need together would be very simple to code for, just as searchable, and would mean no worries about updating old or edited issues - get the code right, then re-index the project once, and it's all done.

Curtis Woronuk · Answer

Hey Warren,

Thank you for your reply! I am working on a script now and will reply when I am done. Thanks again.

Warren_mz9b4z · Answer

Hi Curtis

This sounds like a task that would be suited to the REST API, if you, or someone else, has some programming knowledge. Via this, you would be able to change the Summary of any issue programmatically, using VBA, C#, Javascript ...

See https://developer.atlassian.com/cloud/jira/software/rest/#agile/1.0/ and https://developer.atlassian.com/cloud/jira/platform/rest/#api/2/-getPermissions for details on the API