Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Trigger multiple subtask with different custom fields

Ratan Singh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 19, 2025

I need to create an epic which automatically triggers multiple subtask.

Under each subtask there are multiple questions and a paragraph field to answer.

Each subtask contains multiple different set of questions and paragraph field.

 

What I have done.

Step 1> Created custom field for specific subtask. For example:

SubTask1: Data Resources is a tab under which there are two questions:

1. What Data is required?

2. Data Minimization

Subtask2: Handover and Feedback is a tab under which there are two questions:

1. Handover

2. Feedbacks

Step 2> I have created two issue type Subtask1 and Subtask2.

Step 3> I have created screens, Schema and Work Type Schema.

Step 4> I have associated it with my projext.

But, it still does not work. What next steps can be taken?

1 answer

1 vote
Dilip
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 20, 2025

Hi @Ratan Singh 

To automatically trigger the creation of multiple subtasks with different custom fields when you create an Epic (or any parent issue), you need to use Jira Automation. Here’s a step-by-step guide and some important considerations based on Atlassian documentation and best practices:

Automation Rule Setup

  • Trigger:
    Set the trigger to "Issue Created" and specify the Epic issue type (or your parent issue type).

  • Branching:
    For each subtask you want to create (e.g., "Data Resources", "Handover and Feedback"), add a "Create Issue" action within the rule.

    • You can create multiple "Create Issue" actions, each configured for a different subtask type and with its own custom fields.

  • Custom Fields:
    When configuring each "Create Issue" action, set the values for the custom fields relevant to that subtask.

    • Make sure the custom fields are available on the subtask’s screen and are not restricted by permissions or context.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events