Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

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


1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 02, 2023

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.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events