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...
Brendan G
over 3 years ago
in Releases
0
Future consideration
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...
Kent E
almost 2 years ago
in Releases
0
Future consideration
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...
Ronnie Merkel
over 3 years ago
in Releases
0
Future consideration
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...
Guest
over 3 years ago
in Releases
0
Future consideration
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...
Stephen Morse
over 5 years ago
in Releases
0
Future consideration
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...
Max Cascone
over 7 years ago
in Releases
0
Unlikely to implement
A product owner should have the OPTION to configure a default release capacity at a product level. Teams on an iterative release cycle are likely to have a similar capacity release to release.
Guest
over 9 years ago
in Releases
0
Unlikely to implement
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...
Guest
over 5 years ago
in Releases
1
Future consideration
Allow filtering by assignees in the releases overview
We manage several products at the same time
Each products has several releases.
Each member of our compagny is likely to work on several products.
In the releases overview, I would like to see the features assigned to a specific user to check if...
Yannick Geffroy
over 7 years ago
in Releases
0
Already exists
On occasions, I have had to change the status of a release back to open and then close it again. This resends the release to everyone subscribed. I would like to be able to disable sending a notifications for this type of maintenance.
Rob Bedeaux
over 9 years ago
in Releases
1
Unlikely to implement