Does a cloned EPIC require resaving all decision points in order for automation to work?

[Marshall Ford]

I'm trying to find a way for my team to duplicate the information in a ticket to another, but I dont want the tickets connected, they need to be separate. My question is how to make sure the automation works correctly for the cloned EPIC. 

Also, can Cloning be restricted to a specific stage of my workflow?

[Trudy Claspill · Accepted solution]

Hello @Marshall Ford 

Welcome to the Atlassian community.

Cloning cannot be restricted. There is not a permission associated specifically with cloning.

You asked "how to make sure the automation works correctly for the cloned EPIC."

What automation are you talking about? Are you talking about some automation that was executed against the original ticket? It really depends on the automation rule itself.

[Marshall Ford]

Related to our internal automation rules, which are really complex. So each clone would require "curing" the automation by saving each decision point (there are at least 1/2 dozen of these at the projected stage we'd like to duplicate the tickets) but since we can't restrict the process by stage it's a moot point anyway. Thanks for replying.