Release Phase Dates Determined by all related records
My last idea around being able to adjust Release Phase dates was rejected but our release phases are static (Closed Beta, Open Beta, GA) so simply adding another random phase isn't an option. This level of standardization is needed as we have very...
Guest
over 6 years ago
in Releases
1
Future consideration
Multiple Independant Releases within Master Releases
As an enterprise SaaS software provider, we need to manage releases in two key categories, major and minor, so that we can monitor the iterative delivery of our minor releases as a part of our major, less frequent, releases and provide clarity to ...
James Love
about 2 years ago
in Releases
0
Future consideration
Add field for target release date vs actual release date
It would be helpful if, by default, Aha! could provide a field on releases to track the originally targeted release date. It would also be helpful to then show how many days the release was late by (compared to the actual release date) on the rele...
Guest
about 5 years ago
in Releases
0
Future consideration
Option to move feature / epics end dates automatically with Release date
Currently end dates for features have to be moved individually, when a planned date for a Release is shifted. While this may be useful as a default, it would be really helpful at the stage of high level planning. A checkbox, like for moving featur...
Guest
over 3 years ago
in Releases
0
Future consideration
Have a Release Workflow Custom Status trigger the Send to JIRA action
In the end I just want to be able to manage the Send to JIRA trigger action via either my Features Workflow or my Releases Workflow. Send to Dev to me equates to send to JIRA. I will want to make sure my status is updated throughout, so I will alw...
Guest
over 9 years ago
in Releases
2
Unlikely to implement
Allow group for pivot on repeat release phase names
Right now record values that are consistent are only grouped together if they have a relationship or a common selected value. For those that have the same value manually entered with no relationship, they are included as separate records in a pivo...
Dru Clegg
over 6 years ago
in Releases / Reports
0
Future consideration
Allow the capability of removing automatic alphabetizing for custom user fields
For some projects there are multiple PMs working on the project. Need the capability to add multiple names in the field without the system automatically sorting the order in the field. Lead PM needs to be first in the field.
Belinda McMorran
over 4 years ago
in Releases
1
Future consideration
For a release, you can add a feature to a phase to enable an understanding of how far through a release a feature is. The phases defined are relevant to that release.
A 'product' release can be attached to a master release. This is likely to be a ...
Guest
almost 7 years ago
in Releases
0
Future consideration
I set my releases Gantt view to sort by release date. If I add a new release, it appears at the bottom regardless of the sort order it should be in. If I manually refresh the screen, it remains at the bottom. To have it sort properly, I have to go...
Guest
over 1 year ago
in Releases
0
Future consideration
With the new functionality to assign records in Aha! to Jira sprints using a custom field, it would be great to at least show these sprints on a product plan:
I realise that there are several older ideas related to this, but having this abil...
Guest
about 6 years ago
in Releases
0
Future consideration