Retroactively apply automation to features/ideas that were prior before the rule.
We are hoping to either: 1) Set-up a manual automation trigger for features created prior to an automation rule or 2) Have an option to retroactively apply a new automation rule too all features or just new features.
Noa Braun
over 3 years ago
in Features
0
Future consideration
Feature cards on the features board are colored based on their status. When stakeholders, such as leadership, are browsing the features board, they may not know how the statuses correspond to the color of the feature cards. It would be helpful to ...
Matt Bilan
over 3 years ago
in Features
0
Future consideration
Feature dependencies based on Requirement dependencies
Our engineers have a good view into Jira issue dependencies. Our business process enforces that all Jira issues will belong to a Jira Epic. We then map those Jira Epics into Aha Features. We would like the Jira Story/Task/Bug dependencies to be ro...
Ability to NOT include the Description Field for the Create Template
I am using the new Template capability to provide guidance for populating Initiatives / Capabilities (Features) via a standard format. Unfortunately, to use this feature I am required to include the Description field in the Create Layout. This res...
Peter Bongiorno
over 3 years ago
in Features
0
Future consideration
Ability to add schedule option to feature card at product line level
the ability to see start and end dates of a feature in the board view is very useful - you can set this up at product level but this breaks the ability to manage cards consistently once at product line level (something that is very useful when you...
Guest
about 7 years ago
in Features
0
Unlikely to implement
Remove Epic as mandatory field while a feature is created.
To create a feature I must link it to an Epic before I can save it, but then I can go back and unlink the Epic. If I can go back and unlink the Epic, then why not allow the user to create a feature without linking it to a specific Epic from the be...
Guest
over 3 years ago
in Features
0
Already exists
As we plan our releases, we order features in those releases by their Aha! score. The "Rerank features by" option makes it simple enough to ensure records are in the correct order during planning. As a release plan evolves though, it becomes chall...
Jeff Tucker
over 3 years ago
in Features
0
Future consideration
While someone is doing a bulk edit or delete, you can show a warning or alert on the middle of the screen highlighting the bulk update or delete to avoid accidental updates.
Guest
over 3 years ago
in Features
0
Future consideration