Automation screen

[NoName]

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.

[Clara Belin-Brosseau]

Hello @NoName

As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone issues in Jira. It's automated and easier to set up. You’ll have the ability to select which field should be cloned.

The app allows you to clone Jira issues with all their content (summary, description, custom fields, comments, attachments…). You can even sync the clone and source issue if needed. 

You can check the guide here.

The app is for free during 30 days (and it stays free under 10 users).

[Ash Yadav]

The target project/issue type must have the same screen configurations and custom field contexts. 

Example: Cloning a story issue type from project A into project B will only bring across fields that are visible to both. If a field is not on the create screen in project B, it won't appear. 

There is a good discussion with a solution on this here: https://community.atlassian.com/t5/Jira-Work-Management-Questions/Automation-Clone-Custom-Fields-are-not-cloning/qaq-p/1964939

KR,

Ash

[NoName]

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.

[Trudy Claspill]

Hello @NoName 

We will be better able to advise you about changes to your rule if you provide screen images that show your entire rule, and  screen images showing the details of each step.

What is the project type of the project in which the trigger issue exists? Get that information from the View All Projects page under the Projects menu.

In the Clone step what have you selected for the target project and issue type?

If you have specified a target project that is not the same as the source project, please tell us what the project type is for the target project.

[NoName]

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. 

[Trudy Claspill]

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.