Clone EPIC & Stories to New Epic and link New Stories via Automation

[Melissa Lato]

I have been trying to write a manual automation rule to clone an EPIC (or the selected issue) with all its sub tasks and then link them all as they were in the original EPIC:

I have tried many variations of this but all the Stories seem to stay linked to the original EPIC. I feel like I am so close that someone hopefully will be able to confirm the final steps for linking them up.

Thanks in advance.

[Nic Brough -Adaptavist- · Accepted solution]

They don't "look like duplicates" - a duplicate would mean two fields that contain potentially different data.

They are aliases - one field with two or more names.  The reason they exist is partially because some developers thought it might be good to allow them to use the fields internal name, and partly because users were frequently using the wrong name in searches and it's easier to allow them to do that than explain that you have to use the display name all the time.

[Fazila Ashraf]

Thank you Nic! While i was posting this question, i was actually hoping you would answer this one :)

[Alexey Matveev]

I would add issuekey and key. I ve never seen any differences with such fields.

[Fazila Ashraf]

Good one.. updated the question..