Releases
Sort by:
Trending
Status:
Shipped
Showing 471
2
VOTE
Move Features into Parking Lot Automatically
There are instances where we run into a situation that upon shipping a release, features that are not in done status will move to the next slated release in the workspace. This is not ideal, as features in one release may not relate to the other, ...
0
Future consideration
2
VOTE
2
VOTE
Allow for null Release Date
Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...
0
Future consideration
2
VOTE
Allow child releases for a master release to retain unique names
There are instances where multiple releases exist within the same product workspace that are separated intentionally for visual management. Creating a rollup release causes the children to inherit the parents name, but it would be useful for the c...
0
Future consideration
3
VOTE
Apply Template when creating Release from the Master Release
When creating a child release from the master release, allow the user to apply a product template to the created release. This will allow the Sub-Release to have all of the steps etc. required. Currently, the user either needs to create the releas...
0
Future consideration
2
VOTE
Warn users about the result of a release duplication
Currently when you duplicate a release there is no warning about the consequences of the duplication job (e.g. number of objects duplicated). As a relatively new user I ran into this when I recently duplicated a release, thinking that it would jus...
0
Future consideration
4
VOTE
Feature effort estimate total instead of capacity on Features board
If a release doesn't have a capacity entered, instead of just showing "n/a", i would like to see the total of the estimates for the features in that release.
Extra points: Enable a velocity chart on the feature board. Perhaps a chart can be hacke...
0
Unlikely to implement
5
VOTE
3
VOTE
Recompute or Re-sync logged story points (time) in a release.
A button, when pushed, would recompute the work done and work remaining in a release, based on the current status of feature or requirements within the release.
Presently, Aha's computation of work done is automatic and event-based, i.e., It happe...
1
Future consideration
1
VOTE
Provide A "Quarter" Field for Release Phases & Milestones
Similar to Epics & Features that allow you to group their start/end dates on a "calculated" quarter of the year, the same type of field is useful on releases to show the quarters in which a release phase/milestone will begin. This allows us to...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved