How to have custom fields in a sub task based on the issue type of the parent task?

[Anuj]

I have different types of standard tasks

• Story
• Enhancement
• QA Testing
• Bug

For every standard task, when a sub-task is added, there are only two fields available

• title
• description

I want to have different fields for each sub-task based on the issue type of the parent task

For example:

• QA Testing
  • Steps to Reproduce
  • Expected Result
  • Actual Result
• Bug
  • Reported By
  • Identified in
• Enhancement
  • Developer
  • QA

and so on.

How can I have custom fields for each sub-task based on the parent task's issue type?

I also tried creating a new sub-task issue type

If this is the expected change, then how can I limit the standard task to use specific sub-task issue type when a sub-task is created?

[Valerie Knapp]

Hi @Anuj , thanks for your question.

I would do this with automation, where you can use something like this rule as a base to start from - https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180/26549810 

So, on the creation of the parent type of issue, Bug, for example, you can create two Subtasks and populate them with a predefined Summary, Description and whatever other fields you want.

Then you could have another rule for each of the different parent issue types. It is also possible to use the different subtask types if you want. I agree this can be useful if the different subtask types have different fields and screens.

Please take a look at the rule and share your feedback.

Hope this helps

Cheers

[Anuj]

What if new sub-tasks are added after the creation of two sub-tasks? Also, all parent tasks do not need to have sub-tasks, so why create sub-tasks beforehand that may not be used?

[Valerie Knapp]

Hi @Anuj , thanks for your feedback.

1) If you create other subtasks, you could configure the automation so that nothing would happen if it is only triggered by the creation of the parent type task 

2) It was just a suggestion. I agree there is a risk here you will occasionally create subtasks you don't need with this approach.

Cheers