RELATED IDEAS
I need a way to get features NOT to determine the length of the phase it belongs to
I need a way to not get features to determine the phase length of the phase they belong to. This is making feature management difficult in the release view.
It is also useful in when Features are mapped as EPICs in JIRA and you do not want due dates on them.
1
MERGED
Update dates of phases that cascade dates to features associated with that phase
When I link features to a release phase, if I need to change dates then I have to change the date for every feature associated with that phase. The only other way around this is moving the gantt chart around but it doesn't interact with the phases...
0
Shipped
3
MERGED
Fixed start and end dates of release phases
We work in our program with firm defined scrum sprints of 2 weeks, i.e. each scrum sprint has a firm start and end date. When I add a feature to a sprint, the feature must inherit the start and end date of the scrum sprint (release phase) it is ad...
1
Shipped
We plan releases and what features (stories) go into them in Jira but Aha doesn't inherit the "membership" of a release from Jira in that it doesn't automatically add the features to a release gantt. When we manually add the features, it simply adds one to the end of the other, extending an already planned release out way beyond the end date and it's a real pain in the neck to put all the stories back where they need to be. In my opinion Aha shouldn't do this, it should allow for the fact that we might "import" a release and it's constituent features, even if they don't have start/end dates.