We use release to reflect our Product Increments. As we are synchronizing with AzureDevops we cannot take advantage of the Release Phases. Therefore It would make sense to be able to define a Hierarchy of Releases: e.g. Release PI-5 --> Release...
Christophe Bucheli
almost 5 years ago
in Releases
1
Future consideration
Having more than 1500 products it is time consuming to ship Sub releases one by one.
It would be very helpful to select all (or at least a number) of them at the same time
Monica Rossi
over 7 years ago
in Releases
0
Will not implement
We need the Ability to Mass Edit Release Phase Name
Use Case:
We have 25 product x 25 sprints per year = 625
We incorporate TFS Sprint into (1-25) in each Release Phase Name (which are 1-6 or 7 per release).
The numbers in TFS were updated and sh...
Alex B
almost 5 years ago
in Releases
0
Future consideration
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
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
over 2 years ago
in Releases
0
Future consideration
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
Alexa skill to interact with releases and product strategy
The idea would be to interact with our high level roadmap of releases by asking simple questions to the Amazon Echo like :
- Alexa, what is the state of our [Product Name] release [Release Name]?
-- The answer could be: There are 5 features [ready...
Jean-Francois Potvin
over 7 years ago
in Releases
1
Unlikely to implement
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
Separate Master Release Status and Release Status in feature roadmaps
Currently when I enable Show Release Status in a feature roadmap, it shows both the Master Release and sub-releases's statuses. This is quite noisy. I would like the option to choose one or the other (or both) release type's status to show.
Max Cascone
over 7 years ago
in Releases
0
Will not implement
Feature Board - Release to display the Development Started on Date
In the current view you only see either the release date internal or external, whilst this is great if you have multiple releases it would be great to see the Development Started on date, this helps when you are looking at the Feature Board (NOT t...
Natasha Venter
about 5 years ago
in Releases
1
Unlikely to implement