nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to change Epic summary to flow to child issues

atrout

Hello! I am needing assistance. I am trying to create an automation that if the summary of the epic gets changed at all that it will flow to all the child issues as well. However, the thing that I am stuck on is that each child issue also has it's own summary that needs to stay unchanged. I have done some testing but when I use the copy from parent summary it pushes the name longer and longer because it is not replacing/removing the previous summary before it was edited.

Accepted answers

Trudy P Claspill

Hello @atrout

Welcome to the Atlassian community.

Whenever asking for help with an Automation Rule please provide a copy of the Automation Rule you are working on and the details of each step.

How are you initially copying the Epic summary to child issues? If that is a separate rule, please show us that rule too.

All comments

Trudy P Claspill

Hello @atrout

Welcome to the Atlassian community.

Whenever asking for help with an Automation Rule please provide a copy of the Automation Rule you are working on and the details of each step.

How are you initially copying the Epic summary to child issues? If that is a separate rule, please show us that rule too.

atrout

Thank you for the welcome and quick response!

Here is the screenshot of what is happening- each time I rename the summary, it pushes it over.

Screenshot 1.PNG

Here is what the rule looks like that I added to react to when a summary gets changed.

screenshot 2.PNG

Lastly, this is the rule that has the child summaries that I need to stay with each task:

Screenshot 3.PNG

Trudy P Claspill

Review what I've written below and let me know if I understand your need correctly?

You initially create the child issue via automation and set its summary to

<Epic Summary> Task Summary

Then the first time you change the parent Epic Summary, in its child issues you want to change the summary to be

<Epic New Summary> <Epic Original Summary> Task Summary

And if you change the summary of the Epic 2..n more times then in the child issues you want to just replace <Epic New Summary> with the new Summary from the Epic, and keep in the child issue the <Epic Original Summary> Task Summary text.

Example:

1. Epic created with summary "Original Summary"

2. Child issue created with summary "Original Summary Task Summary"

3. Epic summary changed to "New Summary".

4. Child issue summary changed to "New Summary Original Summary Task Summary"

5. Epic summary changed to "Changed Again"

6. Child issue summary changed to "Changed Again Original Summary Task"

atrout

Perhaps there is a way to flow the Epic summary to the task summaries via a different code and rule so that it doesn't live on each individual task summary?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud