nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

jira - recommendation in handling sub-task of sub-task

Gavin_b342qo

So Jira will not let you create a sub-task of a sub-task. So what is the recommendation to handle the following?

Epic

--task

----Subtask1A

------Subtask1B

------Subtask2B

----Subtask2A

I want to be able to track the "B" tasks which are under Subtask1A.

with due dates, comment essentially all functionality of jira ticket issue A.

thanks

Accepted answers

Gavin_b342qo

So the issue was the resolved by

making the final sub task to an action item

then link that action item to the sub task.

All comments

Nic Brough -Adaptavist-

There is no recommendation beyond "don't do sub-tasks of sub-tasks". In most cases, they are a huge over-complexity, leading to attempts at micro-management and have no real use.

Instead, question the "need" for them. You will almost certainly find out that you don't need them at all. Or, in the case where you do, you are planning at the wrong level, and should be going up, not down

Given your

Epic
- task
  - Subtask1A
    - sub-Subtask1B
    - sub-Subtask2B
  - Subtask2A

Instead use:

Initiative
- Epic
  - Task 1A
    - Subtask1B
    - Subtask2B
  - Task2A

Gavin_b342qo

So the issue was the resolved by

making the final sub task to an action item

then link that action item to the sub task.

Gavin_b342qo

Yeah but I'd essentially be bumping each of the items up to the next level to get the desired framework. However, that would just change the whole defined used of each tier. thanks though.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server