Automation screen

Question

When cloning an issue, what screen is automation using exactly? When I use automation to clone an issue, it creates the issue but the screens are not using the same screen as the trigger issue and has several fields showing that we do not want. I'm looking for guidance on how to fix this so when an issue is cloned, it clones into a similar screen as the trigger issue.

Trudy P Claspill · Answer

Hello @NoName

I have not found any documentation that indicates which fields (or a screen) used to underly the Clone Issue feature. Unfortunately I think you would have to use trial and error to figure that out.

The Clone Issue action in Automation Rules does give you the ability to set other fields as part of the action, and most (I can't guarantee all) fields provide an option to copy their data from another issue to make it easier to get the data you want.

NoName_ffzb3m · Answer

Hence the reason for my question. I was trying to clone a ticket exactly the same. Same project, same issue, etc but clearly automation uses some other screen, it doesn't actually clone the ticket. It may take some of the information but it doesn't actually "clone" it. I'm trying to understand what screen configuration that automation uses when cloning a ticket.

NoName_ffzb3m · Answer

I ended up deleting it because I could not get it figured out so I no longer have screenshots. All I was trying to do was clone a ticket into the same exact project, not a different project. Same exact issue type, etc. I literally just needed two copies of the same exact ticket.

I expect that if I "clone," it will exactly replicate the existing issue, including fields. My issue was that I do not know what screens the cloning/automation uses but none of the custom fields from the ticket I was trying to clone, were visible in the cloned ticket.