Preselect data by agent before ticket is cloned by automation - how?

Question

Hi all,

is there a way to clone a ticket by automation but editing first the summary, description and the attachments before the new ticket is created (in another project)?

Ideally i have a kind of preview of the original ticket that should be cloned and the supporter should edit what should be copied into the new ticket and what not (for data security reasons). When the supporter has done the editing he/she/it confirms (a button) and then the ticket cloned in another project with the selected data.

Any ideas?

Bernd Gurn · Answer

Thanks Bill for your feedback. See also my comment above regarding using an app.

Bernd Gurn · Answer

Offering a solution by a third party is here very popular and always my second choice but thanks for your feedback.

And by the way: as long as the pricing model for apps is still calculated on the user tier amount even if only a handful of user is using the app it´s still not very attractive to us to buy an app.

Luka Hummel - codefortynine · Answer

Hi @Bernd Gurn

If you are willing to try a third-party app, our app Deep Clone for Jira provides a powerful solution for automating and customizing issue cloning, including pre-editing fields before cloning.

With Deep Clone for Jira, you can:

* Use the Field Editor to modify specific fields automatically when cloning a ticket.
* Set up Presets to ensure specific values are applied before cloning.
* Utilize Post Function Cloning in Jira workflows to clone and update issues automatically based on triggers.
* Integrate with Jira Automation to trigger Deep Clone actions with custom configurations.

For your use case, you can configure Deep Clone’s Field Editor to set predefined values before the clone is created. Additionally, using a Jira Expression, you can dynamically set values based on conditions.