Releases
Sort by:
Trending
Status:
Showing 476
5
VOTE
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...
3
Unlikely to implement
4
VOTE
Downstream configuration of terminology
I want to use one set of terminology at the Product Line level and another set within its Products.
ie, Initiatives at the Product Line level and Epics at the Product level.
Allow me to set the terminology for all products in a product line's conf...
0
Already exists
4
VOTE
Bulk creation of Releases
Many marketing teams use Aha! to create and manage their marketing campaigns and roadmaps.
This use-case typically involves representing campaigns as Aha! Releases and generates many more releases than a software development use-case would (typica...
1
Unlikely to implement
4
VOTE
Automate release information between Aha and JIRA
We have monthly releases configured. At the end of month, I move any open stories to the next month. The story reflects the new release, however, the associated JIRA ticket still shows the original release. To resolve, I have to go into the story,...
0
Already exists
2
VOTE
Hide epic reference ID when showing related epics for your feature cards
When displaying epics related to features on the Features (release) board, I would like the ability to remove the epic ID so that only the epic Name is displayed. I use them as visual groupings of features and don't want additional "noise" on the ...
0
Future consideration
3
VOTE
3
VOTE
Include default features in release template
We create a lot of very similar releases. I know that we can copy a previous release, however it would be better to create a release template that is comprehensive, and to select from that release template when creating a new release (launching a ...
0
Already exists
3
VOTE
Add more functionality to Status "on hold" / "project complete"
I would like Aha to stop acting on a release if the status changes to "Project Complete" or "On hold / will not do". Today if I select on hold this has no influence on Overdue dates for example. Assigned people still get daily reminders - that doe...
0
Will not implement
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
2
VOTE
Standardization in release name
Dear Team. We would like to create releases centrally for our entire Product Suite consisting around 20 workspaces. You advised me to consider the roll-up releases function which is great still we have to define our own unified release names manua...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved