| Reporter |
Christoph Neuroth (c089)
|
|---|---|
| Created | Aug 9, 2012 12:46:07 PM |
| Updated | Jun 3, 2013 5:00:25 PM |
| Resolved | Jun 3, 2013 5:00:25 PM |
| Priority | Normal |
| Type | Feature |
| State | Fixed |
| Assignee | Vadim Gurov (vgurov) |
| Subsystem | Agile Board |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | 4.0 |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Undefined |
We tried having a hierarchy like this:
This could be modeled with subtasks, but as soon as Story A is a subtask of Epic I, it will no longer show up on the agile board. Using a custom link relation avoids this, but then they can't be shown in the issue list tree view.
- Epic I
- Story A
- Task A1
- Task A2
- Task A1
- Story B
- TaskB1
- Story A
- Epic II
- ...
This could be modeled with subtasks, but as soon as Story A is a subtask of Epic I, it will no longer show up on the agile board. Using a custom link relation avoids this, but then they can't be shown in the issue list tree view.