Skip to Main Content
ADD A NEW IDEA

Releases

Showing 456

Rules based status changes on workflows

We need a feature that allows the Release status be automatically changed to a "red" or blocking status value based on a rule. An example for a rule would be: If Release date is < than Today AND Release status NOT Equal to Shipped than set Rel...
Christian Stark over 6 years ago in Releases 0 Future consideration

Workspace name is removed from a sub-release in the Release Gantt

Who would benefit? Those using Roll Up releases What impact would it make? It would improve clarity How should it work? This is really a bug - often when the sub-release is expanded the workspace name is removed. It should persist.
Guest 10 months ago in Releases 0 Future consideration

Helpful Insights / Reporting

We would like to be able to extract some insights from our Aha data. For each release: How many points over capacity are we? After the first sprint in a 2-sprint release is completed, are we half way done with story points? How many features do w...
Guest over 9 years ago in Capacity planning / Releases 0 Future consideration

Require approval for changes to certain fields

We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...
Kelly Sebes almost 5 years ago in Releases 1 Future consideration

Ability to apply a custom scorecard to 'Product value' in Aha! Develop

We would like to be able to create and apply custom product value scorecards onto the 'Product value' field in Aha! Develop for work (features) that originates in Develop (the engineering work). Currently this is not configurable and all our Devel...
Jason Gillmore over 1 year ago in Releases 0 Future consideration

Lock release timeframe vs features

I'd love the ability to lock a release's start and finish date, and its children features have to stay within those dates. If they don't provide some kind of feedback or alert that the feature has strayed out of its bounds. Also, in the Releases...
Max Cascone over 7 years ago in Releases 0 Future consideration

Burndown at Master Release level

We need a burndown at the master release level. We have multiple product groups working together and we need to see a burndown for all of the work combined.
Ashley Powell about 4 years ago in Releases 1 Future consideration

Release date changes - require reason and display on retrospective

Who would benefit? Teams analyzing the changes in a release and needing to understand the factors that contributed to date changes. What impact would it make? Better visibility into challenges or themes to impacts on releases. How should it work? ...
Bonnie Trei 10 months ago in Releases 0 Future consideration

Add Feature Lists to Releases/Details/Progress view by sprint

When reviewing the feature burndown (Progress), I would like to see a listing of features completed, upscoped, downscoped in a list form rather then having to hover over the segments on the chart. While hovering is a great feature, it does not all...
Guest over 9 years ago in Releases 3 Future consideration

Have release status update based on Progress

Who would benefit? Those using releases What impact would it make? Less manual work How should it work? Have an option for Release status to update based on progress of features/epics in the release. The progress can change based on settings, so i...
Guest 11 months ago in Releases 0 Future consideration