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 ...
Guest
about 6 years ago
in Releases
0
Already exists
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,...
Bob Lauer
over 8 years ago
in Releases
0
Already exists
Add 'Date' in the view at 'Release>Roadmap' gantt level
We are regularly being requested by our clients can we see the dates and assigned too/tasks in the Gantt view via: Releases>Roadmap. Because we can't show the dates (we can show the letter of the day and the week start date), they then ask us t...
Guest
over 9 years ago
in Releases
2
Already exists
Ability to track progress/status of each milestone and phase within a release - we track overall progress of the release, but tracking where you are within the release would be helpful to show other teams/stakeholders where we are at within the re...
Guest
over 2 years ago
in Releases
1
Already exists
Add ability to display a release description/note on the release plan gantt
Would really like to be able to include a brief descriptor or note within the gantt release plan - specifically for presentations and interdepartmental communication, the release name does not give enough description for most people to properly di...
Guest
over 2 years ago
in Releases
1
Already exists
Add Features of a previous Release to another Release
We're currently release in batches. We're having monthly releases that are delivered to our customers through our Marketplace. Every 3-6 Months we're having a cumulated release where all the features since the last cumulated release are included -...
Fabian Henzler
almost 10 years ago
in Releases
2
Already exists
Allow the 'Will Not Do' Status Category to be Shipped
We use the default 'Abandon' status for Releases, which is a 'will not do' category. This is logical for Releases you are no longer planning to do, however, when you 'Ship' that Release, Aha! automatically updates the status to a different one cat...
Guest
about 5 years ago
in Releases
2
Already exists
Goal : to help feature and requirement traceability in a single document delivered at the conclusion of a release. This could also help identifying feature/requirement coverage
Guest
about 5 years ago
in Releases
1
Already exists
Provide a way to lock/freeze the Feature Board and Releases so only the Product Owner can change them?
It would be helpful if there was a way to lock/freeze the Feature Board and and at least the Release Content so only the Product Owner can change it. Our Platform has very granular Role specifications for example
Bill Dykas
almost 8 years ago
in Releases
3
Already exists