Have workflow status change dates refelect the most recent date a status was set
The value of “Status changed to <status X>” for a feature workflow appears to perpetually contain the date of the first time that the status was changes to <status X> rather than the date of the most recent transition to <status X&g...
David Kettinger
over 8 years ago
in Features
6
Future consideration
Aha! allows you to create feature workflows for a product, but not for a feature type. It would be helpful to have product workflows applicable beyond the product - allowing users to customize completion workflows per feature type.
Let's look at ...
Max Chanoch
almost 10 years ago
in Features
4
Future consideration
Sync status updates between Features and their associated Releases
Currently when any feature changed their status from Backlog to In Progress, the associated Release should be manually updated to reflect the changes. There is a functionality to sync status updates between epics and their associated features, and...
Guest
over 3 years ago
in Features
2
Future consideration
When viewing an individual feature card (especially after searching for a feature) it is easy to lose context of how important that particular feature is, since you cannot necessarily see it listed against all the other features in the feature boa...
Robert Wood
over 4 years ago
in Features
4
Future consideration
Aha should delete the integration link when receiving a delete trigger from a webhook
We have Aha linked to JIRA. When we delete an issue in JIRA, this triggers our Webhook to send a message to Aha. I understand and agree that this should not cause Aha to delete the Feature connected to it for security reasons. But I would expect A...
Marvin van Dongen
over 8 years ago
in API / Features
8
Future consideration
Ability to tie color feature color to other fields
Status doesn't help to organize we would rather color code based on priority. We created a custom field for this and are eventually planning to use scorecards. We would like the ability to tie the color of the feature card to other fields beyond s...
Nick Galassi
almost 7 years ago
in Features
15
Future consideration
We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field...
Guest
over 7 years ago
in Features
6
Future consideration
As business needs change a Feature that seemed obvious to add to a release pipeline may get tabled based on new information and based on more information may need to be demoted. Even though Features can be bulk moved to Ideas the ability to easily...
Aaron Bawcom
about 10 years ago
in Features
8
Future consideration