using automation to clone ticket on transition, can i prompt for required fields?

[Colleen Cosgrove]

I would like to be able to send a customer ticket "to development" which will create a ticket in a development project and set the link to a specific type.  I am doing through automation on the transition, but the new project has required fields that the original project does not.  Is there a way to prompt for those fields and set them in the cloned ticket

[Luka Hummel - codefortynine]

Hi @Colleen Cosgrove

If you're looking to clone a ticket on transition and need to handle required fields in the new project, our app Deep Clone for Jira could be a great solution.

Unlike standard Jira automation, which doesn't allow user prompts during transitions, Deep Clone offers more flexibility. With Deep Clone's Post Function Clone feature, you can automate the cloning process as part of a workflow transition and predefine how required fields are handled. This way, you don't need to prompt the user manually; instead, you can configure the fields to be populated automatically based on your needs.

Additionally, you can leverage the Field Editor to adjust fields in the cloned issue, ensuring that all required fields are properly set even if they're not present in the original ticket.

[Clara Belin-Brosseau_Elements]

Hi @Colleen Cosgrove

As an alternative to Automation (that can be really complex sometimes), I can suggest trying our app Elements Copy & Sync. It allows you clone a customer ticket to another project (here development project) based on a status transition.

You can choose which fields should be cloned and you can even sync them together if needed so that your support and dev teams can collaborate more efficiently on the issue.

Don't hesitate to check the documentation, it’s really quick and easy to set up.

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

[Trudy Claspill]

Hello @Colleen Cosgrove 

The only Automation Rule trigger that allows for prompting the user to provide inputs is the Manual trigger.

The Issue Transitioned trigger does not support prompting a user for inputs.

Given that the fields are required in the issue you are creating, with the Issue Transitioned trigger being used you would need to fill the fields without input from the user by

• explicitly selecting static values or
• evaluating the information available in the trigger issue and setting the values in the new issue based on that information.

[Colleen Cosgrove]

thank you. I am ok with using a manual trigger rather than a transition and I see where you can prompt for input... but i want the prompt to use the fields of the project creating - allow them to select from the dropdown list - is there a way to do that?

[Trudy Claspill]

No, it is not possible to tie Manual trigger user inputs to get information from an existing Custom field..

You would have to manually recreate the destination issue selection list fields as user input prompts in the Manual trigger. Only single selection lists are supported for user input list prompts. If the selections options were changed for the field context for the destination project then the user input setup in the Manual trigger would need to be manually updated to match.

[Stanley Duback]

Hi Colleen,

I do some similar workflows to clone issues into other projects and attach them, when creating the automations for the under the action for cloning the issue there is a cog under the Summary box that allows you to choose fields to set. Are the fields that you are attempting to set not present in this box?

You can set up a screen to activate on transition if that information is NOT present. To collect that information, then have the field selected to copy the information presented on the trigger issue.