Content
View differences
Updated by Sven Kunze over 4 years ago
# Situation
As of now, users can filter by a parent but not by an ancestor. This becomes necessary as soon as a WBS hierarchy spans more than one level.
# User Story
**As** a project manager
**I want to** create views with all descendants (children, grandchildren, etc.) of a work package
**so that** _I can focus on and track the progress of an isolated part a project (e.g. a "work package" of a research project)_
**Acceptance criteria**
* _Work package filter ("Descendants of..." or "Subordinate work packages of...") which allows users to see all descendants of one or multiple selected work packages._
* Let users select parent work packages based on the ID
**Optional**
* Let the user specify the depth of the hierarchy (the youngest generation) that should be included and beyond which descendants ancestors should be excluded by the filter.
As of now, users can filter by a parent but not by an ancestor. This becomes necessary as soon as a WBS hierarchy spans more than one level.
# User Story
**As** a project manager
**I want to** create views with all descendants (children, grandchildren, etc.) of a work package
**so that** _I can focus on and track the progress of an isolated part a project (e.g. a "work package" of a research project)_
**Acceptance criteria**
* _Work package filter ("Descendants of..." or "Subordinate work packages of...") which allows users to see all descendants of one or multiple selected work packages._
* Let users select parent work packages based on the ID
**Optional**
* Let the user specify the depth of the hierarchy (the youngest generation) that should be included and beyond which descendants