View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023779 | mantisbt | roadmap | public | 2018-01-04 06:01 | 2018-01-04 06:40 |
Reporter | jensberke | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 2.10.0 | ||||
Summary | 0023779: Tickets not displayed at all or at the wrong position in roadmap when parent-child hierarchy has more than two levels | ||||
Description | Problem When there are tickets which are blocking multiple other tickets, which then again are blocking other tickets (which means at least three levels of parent-child dependencies), the tickets which are blocking multiple others are not always displayed at all, or not at the correct position, in the roadmap. Two simple examples have been attached. One shows two "Parent" tickets, which both depend on the same "Child" ticket and indirectly depend on the "Grandchild" ticket. However, the roadmap only displays the "Grandchild" ticket the first "Parent" ticket, not for the second one. If I'd edit the "Parent 2" ticket it'd be displayed as the first ticket in the roadmap and the "Grandchild" ticket would then be displayed for "Parent 2" instead for "Parent 1". The second attachment shows a sightly different hierarchy with two children. "Child 2" is blocking "Parent 2" but it is also configured to block "Child 1". The latter, however, is not displayed. Instead, "Child 2" appears at the main level on top of the roadmap. If I'd remove the dependency of "Child 1" to "Grandchild", "Child 2" would be displayed correctly as a blocking "Child 1". Expected behaviour The roadmap should always display all children of a ticket, going down all levels of the dependency tree. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||