How to add "Epic name" value to child issue summary with Jira automation?

[Stella Marie Alice Bakhoff]

Hi

I am using Jira Software Cloud and I have a problem with creating an automation.

The goal is to set up an automation rule that would automatically copy "Epic name" value and add (not override) it to child issues' "Summary" field that are created to this Epic. 

I have tried several configurations but end up nowhere. Current rule set up is:



But I get an error saying that the operation "Add" is not supported for "Summary" field.
And according to the advanced field editing documentation the operation "set" would override any existing value.



How could I solve this?

Thanks in advance
Alice
 

[Jack Brickey · Accepted solution]

hi @Stella Marie Alice Bakhoff , will the following not work? 

choose to update the Summary field and use the following or similar...

((epic.name)} - ((summary)}

[Jack Brickey]

note i have not tried to form a rule but can if needed.

[Bill Sheboy]

Hi @Stella Marie Alice Bakhoff 

Yes, and...to Jack's answer:

First thing, the Epic Name field is currently only used for company-managed projects.  Is that what you are using?

Next, the Epic Name field is being sunset (I believe by the end of year).  Instead company-managed projects will work like team-managed project epics, where they only have a Summary without the Epic Name.  Please consider that as you name your epics and write rules.

Finally, based upon your rule structure with a branch, you will want to get at the epic name using the parent smart value.  So to do what Jack suggests, please try this:

• try using the field edit without the advanced edit with JSON in Additional Fields
• instead, type/paste in this smart value:
  • {{issue.parent.Epic Name}} -- {{issue.summary}}
  • or... 
  • {{issue.parent.summary}} -- {{issue.summary}}
• the value will appear below the field, and then you may select it for use in the edit

Kind regards,
Bill

[Stella Marie Alice Bakhoff]

Hi

Yes, the project type is company managed. Thanks for the info about "Epic Name" sunset in the future.

The rule did not work with the branch so I removed it. Everything works as expected with both smart values that Bill suggested:




Thanks a lot! :) 
Alice
 

[Bill Sheboy]

Well done, Alice!

My mistake was not referencing using {{triggerIssue}} as the source when inside of the branch, and you figured it out  :^)

As some follow-ups:

• Would you expect your epic's name/summary to ever change?  If so, you would need an additional rule, triggered on epic changes, to find/update the child issues
• Would you expect an issue's epic parent to change?  That is, a story moves to a different epic, or is assigned to one after create.  If so, you would need another rule to manage that situation.

Edge cases like this are the tricky parts when replicating information, like Epic Name, as part of other issues.

Thanks,
Bill

[Stella Marie Alice Bakhoff]

Thanks, Bill!