Show Release Phase as Available Field to Include on Feature Custom Layout
In creating a custom feature layout for use within a product, the release is shown by default but there is no way to show the Release Phase. The only way that you can then assign a release phase is to drop down the ellipsis, Link to Release Phase,...
Lexy Kassan
about 6 years ago
in Features
1
Unlikely to implement
Ability to choose how each Aha Initiative/Feature/Requirement should be mapped to JIRA, as opposed to one mapping setting for an Aha product.
As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...
Guest
almost 10 years ago
in
0
Unlikely to implement
After a certain period of time, it is no longer helpful to see a release that has been shipped. It should be possible to "archive" a release so that it no longer is visible in dropdowns, the release list, or the feature board.
Guest
about 11 years ago
in Releases
1
Unlikely to implement
This idea encompasses a big picture echoed in a number of idea requests.
The To-Do' feature in Aha! really seems to be an afterthought compared to the other record types in Aha! such as Goals, Initiatives, Features etc. Specifically
To-Do's don...
Jeff Shood
over 7 years ago
in To-dos
2
Unlikely to implement
Need the ability to add COMMENTS to a Release Template
I need the ability to add Comments to a Release Template.
By adding a static comment to a Release Template, I would be able to provide additional instructions to the end user regarding the use of the template, links to additional information, an...
Joe Carpenter
about 6 years ago
in Releases
1
Unlikely to implement
Option to remove requirement of an email address when submitting an idea
Using Aha! to build out a survey in the Ideas Field and would like to remove the requirement for users to have to enter their email, so users could feel as if the ideas are anonymous.
Guest
over 7 years ago
in Ideas
1
Unlikely to implement
When moving a feature from one release to another, the progress should not count against the capacity of the new release.
Often times a feature is not completed within a given release, and it must be moved to the next release. Currently, if a feature has an estimate of 100p and 50p are completed in one release, then that feature is moved to a new release, all 100p ar...
Guest
about 6 years ago
in Releases
0
Unlikely to implement
Google Data Studio turns your data into informative dashboards and reports that are easy to read, easy to share, and fully customizable. Dashboarding allows you to tell great data stories to support better business decisions. I would like AHA to h...
Alex Horan
over 7 years ago
in Integrations / Wanted
0
Unlikely to implement
You should be able to set at default release phase for a release, so that all features added to this release ends up in the default release phase. This would gratly simplify and make the prosess more efficient. Now you have to move new features in...
Guest
about 10 years ago
in Releases
3
Unlikely to implement
better redmine integration - requirements are children of features, and tasks are children of requirements
redmine integration is very helpful and needed.
"When a feature is copied to Redmine one issue will be created for the feature. If the feature has requirements then each requirement will also be sent as an issue."
there should be a way of re...
Michael Martini
about 10 years ago
in Integrations
0
Unlikely to implement