Multiple Sub-Task Types Question

[Preston Warden]

I have a project which requires 15 sub-tasks (as of right now). I am trying to identify the best way to set this up. The project identifier is PPW

• PPW-1 Contract 1

Department Responsible: Supply Chain

• Sub-Task 1
• Sub-Task 2
• Sub-Task 3
• Sub-Task 4

Department Responsible: Engineering

• Sub-Task 5
• Sub-Task 6
• Sub-Task 7
• Sub-Task 8
• And so on

Each of the sub-tasks have a different objective with different fields. Which is better? Create each of these with their own sub-task issue type or is there a better way?

[Trudy Claspill]

Hello @Preston Warden 

When looking at creating issue types and fields you should try to create reusable entities. When you say "15 subtasks are required" do you mean 15 subtasks in each parent issue, or do you mean you are thinking about creating 15 different Sub-task issue types? Creating 15 types of sub-tasks with different field configurations will become a nightmare for maintenance and extension.

You said each sub-task has different objectives with different fields. Can you work with generic fields that can be used across the different sub-tasks to gather different information? Could you create fewer types of Sub-task issue types to re-use across the 15? Do you need to set fields as Required depending on the sub-task objective?