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?
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.