Either sub-phases or the ability to select multiple phases and group them together. My 2 cents - the way I think about it is if I could start out with a template or start out by adding a bunch of phases, inevitably I will have a lot of phases and my gantt view looks busy/confusing/etc. Next step would be to organize by clustering the phases into logical groups. So the idea of creating a sub phase would get the job done but I think of it more as being able to create a grouping of phases and being able to add/remove phases from the group. One level grouping should suffice for my needs as opposed to having multiple layers of nesting.
Using the Feature as a way to nest is possible but it just doesn't make the most sense especially from a reporting perspective. I have reports based on Features and already i've got a lot of people creating Features that aren't actually Features.
The motivation for me is that I want the Gantt chart to communicate the plan in a clear way. Features should be Features. Phases and Activities in the Gantt chart should just be Phases and Activities. And then TO DOs are great but TO DO's can't be represented on the Gantt chart and for many users that are visual, being able to represent key phases and activities on the Gantt chart is important to conveying the right messages.
In my organization, we attempting to achieve parity with other competitive tools so we can replace them with Aha! Having the ability to tie in standard sub-phases into planned releases would allow us to better distinguish work timelines, as well as provide more wholistic, single-team visibility to our executives. It appears that this request was opened in 2016 with idea APP-I-2991, but at the time, it was not prioritized.
We have our sprints defined as release phases and therefore would need sub release phases to add certain events or activities which happen within the release phase.
Rebecca Schneider
almost 2 years ago
in Releases
0
Future consideration
1
MERGED
Gantt : Allow Child Phases with Expand / Collapse menu
Merged
What is the challenge? Without this feature, everything is at the level 0 / parent level, and if, as a project manager, I want to create a detailed plan, then it becomes very tough to do so and all the information will be shown without the way to ...
Guest
13 days ago
in Schedules
0
Future consideration
11
MERGED
Add Sub-Phases to Releases
Merged
When creating releases, I can add existing Features under the Development release phase and these appear indented in the display.
I would like the ability to create indented sub-phases under other release phases so that I can clearly display the u...
Mat Wood
over 8 years ago
in Releases
2
Future consideration
Either sub-phases or the ability to select multiple phases and group them together. My 2 cents - the way I think about it is if I could start out with a template or start out by adding a bunch of phases, inevitably I will have a lot of phases and my gantt view looks busy/confusing/etc. Next step would be to organize by clustering the phases into logical groups. So the idea of creating a sub phase would get the job done but I think of it more as being able to create a grouping of phases and being able to add/remove phases from the group. One level grouping should suffice for my needs as opposed to having multiple layers of nesting.
Using the Feature as a way to nest is possible but it just doesn't make the most sense especially from a reporting perspective. I have reports based on Features and already i've got a lot of people creating Features that aren't actually Features.
The motivation for me is that I want the Gantt chart to communicate the plan in a clear way. Features should be Features. Phases and Activities in the Gantt chart should just be Phases and Activities. And then TO DOs are great but TO DO's can't be represented on the Gantt chart and for many users that are visual, being able to represent key phases and activities on the Gantt chart is important to conveying the right messages.
This is a most on any Gantt application presentation.
In my organization, we attempting to achieve parity with other competitive tools so we can replace them with Aha! Having the ability to tie in standard sub-phases into planned releases would allow us to better distinguish work timelines, as well as provide more wholistic, single-team visibility to our executives. It appears that this request was opened in 2016 with idea APP-I-2991, but at the time, it was not prioritized.