Task hierarchy approach shall be updated
Description
relates to
Activity
Show:
Mariia Korolishyna 1 September 2022 at 16:33
Grouping by field
We are moving from bottom up and checking task fields (everything but hierarchy) --one level at at time, till the very top
No field information information on the top --> "No" folder
Task hierarchy
We are going to follow the approach on checking the closest parent for a task. Meaning, if a task has a defined parent, it will be placed under the parent task.
In case there is no defined parent for a task, we are going to check for a grand-parent (one level up), and so on.
In case when there is conflict we prioritize parent
Epic Link works as field: looking for task own properties
Hierarchy Epic works as hierarchy: looking for parent
With a new approach, the task hierarchy shall work, following the next principles:
first. we are collecting all information about the issues included to a chart
having the task information, we start building hierarchy from the bottom
we check the next available parent for the lowest level task, and place the task under the parent, ignoring
defined grand-parent
in case no parent is set for a task, we look for a grand-parent; if no grand-parent is set, we look for a great-grand-parent and so on