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

[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.

[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.