Toggle 'Off' Automatic Inclusion of features to Releases Gantt
I use the gantt to plot release phases and don't always include features in that process. Automatically including every new feature on the releases gantt can be tedious manual removal process after the fact. I would prefer to add features to my ga...
Adam T
over 6 years ago
in ReleasesFuture consideration
Copying a release should let you select a release date
It is a common practice to create releases containing features in the parking lot to serve as templates. Ex: weekly/monthly releases with recurring tasks to complete. Currently on the features board, if you add a new release, choose the option to ...
Todd Meyer
over 6 years ago
in ReleasesFuture consideration
The change on the Release Details view to 'Quick Links' instead of simply viewing the release-specific gantt, is not a user friendly view & causes extra workflow steps to see a View our team is used to inherently seeing on one screen. The best...
Guest
over 6 years ago
in ReleasesFuture consideration
Allow the 'Will Not Do' Status Category to be Shipped
We use the default 'Abandon' status for Releases, which is a 'will not do' category. This is logical for Releases you are no longer planning to do, however, when you 'Ship' that Release, Aha! automatically updates the status to a different one cat...
As a product manager I want to hide sensitive product data from other users
Aha is used for requirements and planning but I don't necessarily want all of my engineers having a deep look at the financial risks in the project. Similarly I would like to be able to do resource planning on roadmap items without notifications o...
Mark Gerrard
over 6 years ago
in ReleasesUnlikely to implement
We have different teams that work around the clock in the each release. I need to be able to track per release the capacity so I can visualize each team individually and as a whole.
When converting recors, leave traceability like with idea promotion, and close original item
It would be very useful for me to be able to see the original item that gets converted, ie a feature to a release, or vice versa. This is a great feature that you can do this in the first place, but my team would get a lot of use out of having the...
Goal : to help feature and requirement traceability in a single document delivered at the conclusion of a release. This could also help identifying feature/requirement coverage
Add field for target release date vs actual release date
It would be helpful if, by default, Aha! could provide a field on releases to track the originally targeted release date. It would also be helpful to then show how many days the release was late by (compared to the actual release date) on the rele...
Guest
over 6 years ago
in ReleasesUnlikely to implement