Releases
Sort by:
Trending
Status:
Showing 470
9
VOTE
Allow Features in Release Templates
I'm not sure why it's not possible to have features in release templates. Phases and milestones are nice, but features are what actually have the status. This would be especially powerful for recurring releases. For example, I'm manually creating ...
2
Unlikely to implement
20
VOTE
Burn *Up* charts for Sprints, Releases, Epics, and Features
My company would find it useful to have Burn *Up* charts that show how the effort completed is tracking against the scope of a release / master feature / feature For more on the requirements for a Burn Up chart and why it is more useful than a Bur...
2
Future consideration
17
VOTE
Filter Releases on Feature Board
I added a custom field to Releases for Project Type and created a filter for it on my Feature Board; however, when I select the Project Type I want to see on the Feature Board, it still shows all of the Releases for the product, regardless of Proj...
5
Unlikely to implement
7
VOTE
Add field to capture date of "last change" on internal and external release date
Changes in release dates need to be communicated to several stakeholders. If there was a "last changed date" field for both the external and internal release dates, a report could be generated to show all release dates that have changed in say the...
1
Future consideration
21
VOTE
Allow sub-releases to have independent release dates from a Rollup Release date
We're operating in a CI/CD environment, and prefer to release "releases" (especially API's) as soon as they clear integration and performance testing. Forcing all of the sub-releases in a Master Release to inherit that release date is not meeting ...
11
Unlikely to implement
18
VOTE
Add a start date for to-dos
I love having To-dos on release phases as a sort of checklist (and, well, task list). But, usually only say one of the 5 or more to-dos can actually be done at any given time. I'd like to be able to set a start date for to-dos so that they don't a...
6
Future consideration
2
VOTE
Retrospective should ignore records that were moved in with "Will not implement" status
Who would benefit? Product Owners and Project Managers What impact would it make? This would reduce the list of records shown as "incomplete" when the records were added to the release after already been assigned "Will not implement" How should it...
0
Future consideration
1
VOTE
Allow Team to be set at the Release level
What is the challenge? We cannot associate a Release with a Team What is the impact? We cannot do necessary analysis in assigned Releases, commitment and deadline scores etc - stuff outside of Capacity. Describe your idea Allow the core Teams fiel...
0
Future consideration
9
VOTE
21
VOTE
Correlate and sync release phases with jira sprints (or releases)
Right now the aha release phases just seem like an informational overlay with no connection to the features themselves or their JIRA equivalents. So when work gets estimated in jira or progresses these timelines don't change. I have to keep them i...
3
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved