Skip to Main Content



Showing 408 of 7020

Set capacity per team per release

Capacity for teams is currently available to set up at a 'global' level - number of hours per day per week. It would be helpful for teams that are planning releases with multiple teams, to be able to set a capacity for each team per release. Once ...
Madeleine Black about 2 years ago in Capacity planning / Releases 3 Future consideration

Allow nesting of rollup releases

Rollup releases are very useful in organizations with complex and nested product lines and products. A top level product may have a V2.0 which is a rollup of three subsystems, a perfect use case of a rollup release. If each of the subsystems, in t...
Bastian Schoell 2 months ago in Releases 0 Future consideration
150 VOTE

Support Release Notes

Given the astounding amount of work I've seen that goes into making Aha's own stellar release notes comprehensive, detailed, and rich with media, I thought first-class support for release notes might be a nice addition to our workflow–as well as o...
Christopher Keele about 6 years ago in Releases 15 Future consideration

Release phases on feature board

When we go through our PI planning, the feature board is a very powerful tool to move items across and keep a constant watch on the capacity. Every release of ours has sprints and phases but since we do not have the phases or sprints available, we...
Arun Kalyanaraman 15 days ago in Releases 0 Future consideration
161 VOTE

allow capacity planning by product line

We share development resources across several products, and capacity planning by product is of limited value. Enabling an option to set and track of capacity at the master release level would be very helpful. Ideally, capacity within subreleases w...
Guest over 7 years ago in Releases 7 Likely to implement

Capacity Planning by Master Feature Estimates

Often when new Feature requests come in they are at, what we consider to be the Master Feature level...basically an Epic. For future releases, we hold a Release Planning session where our engineers apply high level estimates to Master Feature that...
Guest almost 5 years ago in Capacity planning / Releases 14 Likely to implement

Give a prompt to users before removing shipped releases from view

Automatically removing shipped releases is not acceptable Such a big action should at least require users to agree to this change There's no easy way to find shipped releases This is a basic rule & also poses accessibility challenges https://w...
Guest 20 days ago in Releases 0 Future consideration

Ability to add custom fields to the Release Phase view

In the context of a Launch Plan, Release phases can be used as work items, that together, make up the entire project plan, to come to a successful release. Examples of custom fields: a Release Phase can be assigned to a department and to an indivi...
Guest over 5 years ago in Releases 19 Future consideration

Automation be able to select other field's value

I would like to be able to sync up the release date field with the external release date. When I use automation to try to do this, I am only able to select the current date or a date based on the current date. I would like to be able to set it as ...
Dale Crane 4 months ago in Releases 1 Future consideration

Extend Workflow View to Releases

We want to view our releases in a Kanban-style workflow, in the same way that we can for Initiatives, Epics and Features. This would support the way we work and streamline it across all levels of the hierarchy.
Marcie Gardner about 2 months ago in Releases 0 Future consideration