Overview
Artifacts ("tasks") displayed in the roadmap widget can have children (artifact link with type _is_child).
When the roadmap is displayed, the children are not displayed.
User can expand a task to see its children. A REST call is made to roadmap_tasks/:id/children to retrieve a paginated collection of TaskRepresentation.
Only one level of children is displayed.
In the Links selector, we need to remove the possibility to display children.
Edge cases
Weird Hierarchy
Given hierarchy like:
graph TD
Epic1:::epic --> Story1:::story
Epic1:::epic --> Epic2:::epic
Epic2:::epic --> Story2:::story
Epic2:::epic --> Story3:::story
Epic3:::epic
Epic4...:::epic
ThemeA --> Epic5:::epic
classDef epic fill:#ecfaf6,stroke:#28c4a0,color:#00775c
classDef story fill:#f8eccc,stroke:#f18e06,color:#774a0a
Epic2 shouldn't be displayed in first place because it should appear as a child of Epic1. The general rule is:
- Given a selected tracker (eg.
Epic)
- Display all artifacts that doesn't have an element of selected tracker as parent
-
Epic1 has no parent => displayed
-
Epic2 has a parent, it's Epic1 => not displayed
-
Epic5 has a parent, it's a Theme (not Epic) => displayed
Needed mockups
- Caret to expand/collapse children
- Error state when the list of children fails to load