How to use a mandatory screen scheme when creating a subtask via automation

Tara MallonBrown

I have created an automation to generate a subtask when a status is selected for an issue type (Story).  In this case the status transition is from 'ready to test' to 'failed' which generates a subtask 'defect'.  However I cannot seem to apply a screen scheme or mandatory field requirement to the automation / creation of the task. 

If I add the screen scheme into the transition workflow, it does not add the data to the subtask it just either adds nowhere or to the parent if the field exists

 

Trudy P Claspill

Hello @Tara MallonBrown 

Welcome to the Atlassian community.

Can you provide more information about your scenario?

When an automation rule executes a Create Issue action it does not present a screen for a user to interact with, so there is no reason (and it is not possible) to apply screens or screen  schemes directly automation rules.

When you apply a screen to a Workflow Transition, the data you enter will be added to the issue that is being transitioned.

If you want that data added to a subtask that is subsequently created by an automation rule, then within the Create Issue action in that rule you need to copy that data from the trigger issue (the parent issue) where the data was recorded during the transition.