We need the ability to include subtasks of subtasks (nested subtasks) in time reporting and tracking, even if they are part of multiple lists. This functionality is especially important for software development teams that structure work as follows:
  • Tasks: Represent EPICs.
  • Subtasks: Represent components of the EPIC.
  • Nested Subtasks: Represent individual development items.
Currently, while nested subtasks work as intended, time reporting is impacted because the root (home) location of the nested subtasks remains tied to the EPIC list rather than the sprint or project list where they are actually worked on.
This creates issues for accurate time tracking on sprints and client projects. The desired enhancement would allow time tracking to correctly attribute effort based on the context of the sprint or project list, rather than the root EPIC list.