What is The Use Case For Creating an Issue Type as a Subtask in JSW

[Franklin]

I've been using Jira Server / Data Center for 10 years, but I'm relatively new to JSW. What's the use case for creating an issue type as a subtask rather than just create a child issue subtask inside a talk?

[Bernd Anderer · Accepted solution]

A Sub-Task can only "exist" in relation to a parent. So their connection is much different from a relation between two Standard Issue Type. 

Usually it is used to break down e.g. Stories into smaller work units. Also it provides you additional functionality like summing up your time spent, from the sub-tasks into their parent.  Also, you can not move the parent without the Sub-Tasks.

When you create s Sub-Tasks the relation to their parent is automatically created, while there is not relation between to Standard Issue Type, you need to add that manually. And for Jira that relation does not automatically mean anything. 

Also, Sub-Task is the final hierarchy level, there is no Sub-Sub level.

Does that help you?

[Matthew Chapman · Accepted solution]

Hi There,

I use subtask types to simplify time entry, example we have a call that has both billable and non-billable time. The main issue is created as a task, and then I'll add a subtask/non-billable so we can record all time and comments on the call. 

Another use is to have a parent task to manage the support call/project task, and add subtasks to represent different activities with that, example to provide handheld scanners to a customer I can set up a main task and include these as sub-tasks as they may be assigned to different people:

- Scope

- Set-Up IIS Server

- Provisioning

- Software/Configuration

- Sign-Off & cut-Over

For me, it simplifies the number of tasks I need to manage and report on, my reports can be at task level, but the details are there to track the sub-task progress, hope that helps.

[John Fetzik]

We have some teams that have a "QA Sub-Task" for tracking time spent developing new test cases/scripts.

[Robert Condon]

Out of the box there is only one sub-task type. Creating more allows you to have different sub-tasks with different workflows/automation/reporting/etc

[Anne Saunders]

This. I use Approval Sub-tasks on a project where we have multiple levels of approvals across the workflow and Maintenance Sub-tasks for recurring support activities that relate to a parent maintenance issue. I can use filters and automations with them more easily because they are discrete issue types.

[Nic Brough -Adaptavist-]

That's only true for team-managed projects.  Company managed projects can have many sub-task types.

[Cinthia Catalani]

I am an Admin in an Analytics instance. I am running a PoC in the sandbox with sub-task types. The main feedback I collected from developers was their specific icons for Power BI, Microstrategy, ETL, and Azure, which they considered a time savior.

Also, I will use them to create reports/dashboards in order to measure their workload and maybe to map existing dependencies among some types.

Additionally, I can also create automation, based on the sub-task type.

[Anne Saunders]

That's really nifty - I may start using the different icons to show hosting solution-specific sub-tasks for our routine maintenance work.

[Cinthia Catalani]

@Anne Saunders, it is helpful when they see the list of sub-tasks in the parent issue, especially for teams that move them on the board.

Btw, you just reminded me that I also created automation with them. Before I had a validation in my automation to check if the issue already had sub-tasks, but now I can specify which type.

[Franklin Vaugn]

Thanks for everyone's replies. I read them all and understand the use case better now.