Once development on a release is underway, things happen. Change Control should encompass approvals and permissions to edit dates and schedule, and rollback. Here are some requirements:
1. A product owner (or an "uber product owner", e.g. the VP o...
Guest
over 10 years ago
in Releases
1
Unlikely to implement
i have set the phases up with specific colours to help with identifying the different streams of work for a release; however, the 'view colours' options don't include custom colours, only 'status', 'assignee' and progress.
Andrew Pearson
about 2 years ago
in Releases
3
Already exists
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 6 years ago
in Releases
0
Will not implement
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 8 years ago
in Releases
0
Already exists
Not sure how to remove a sub-release from a roll-up release
Attempting to manage multiple componet release using the roll-up release feature. However, it seems that any accidental addition of a sub-release cannot be undone
Darrell Massie
about 4 years ago
in Releases
0
Already exists
Repeated milestones can be added to release Gantt chart
We have a need to add the same milestone to a release multiple times without creating a new milestone, so that it's shown in the same swim lane (illustrated by the red dots in the attachment)
Guest
about 2 years ago
in Releases
0
Future consideration
Ability to Define and Visualize Capacity of Release Phases
We are an agile software company that releases on a cycle of 3 sprints, each 2 weeks long. We can set our release capacity based on the # of development hours to determine about how many features we can commit to, but we also need to plan how many...
Guest
over 10 years ago
in Releases
3
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 6 years ago
in Releases
1
Future consideration
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, ...
Anh Truong
over 4 years ago
in Releases
0
Future consideration