Automatically create new copy features in other workspaces based on feature tags
Who would benefit? Any product owner that has multiple workspaces or multiple tiers of workspaces. What impact would it make? Reduce the amount of work by creating tickets once instead of copying and moving. Further, changes in the feature in one ...
Guest
about 1 year ago
in Features
1
Unlikely to implement
Our team needs an straightforward, one-click way to share feature URL's between each other. This functionality should ideally be available in all feature listings.
Guest
over 9 years ago
in Features
0
Unlikely to implement
Allow a change in Feature Rank to trigger Automation
Aha currently provides no good way for us to be aware of when the Rank changes. Knowing what the current Rank isn't good enough. I realize this can be seen in Feature History. But, it isn't feasible to have to regularly check the History of all Fe...
Roger Oliver
almost 5 years ago
in Features
0
Future consideration
As a Product Manager, I want the ability to clear or delete field values in bulk so that I can easily clean up errors in my data and ensure that Aha! is the definitive source of truth.
Nathaniel Collum
about 7 years ago
in Features
0
Unlikely to implement
Feature board containing different filter-based lists for backlog management
Combine the List filtering capabilities with the feature board's management capabilities: so I have a board, but instead of moving around in explicit releases for a single product, I can define "feature groups" based on filters (like the List fitl...
Guest
over 9 years ago
in Features
0
Unlikely to implement
Who would benefit? What impact would it make? How should it work? Under each feature name there is a line called "Created by" with the feature creation date and creator's name. This real estate could be better used if this was just included in the...
Guest
about 1 year ago
in Features
0
Future consideration
Indicate confidence metric with score on feature card
With the new confidence metric available on scorecards and the ability to adjust a score over time, when reviewing relative scores on a feature board (and elsewhere that scores appear) it would be useful to see an indication of the confidence leve...
Tim Sachs
over 2 years ago
in Features
0
Future consideration
As a user I don't want my requirements sent to JIRA (or other integrations) if they're marked as Will not implement
I often mark requirements as "will not implement" in Aha (rather than deleting them) just to keep a trail of requirements we've discussed but decided aren't needed. Then when I push to JIRA from Aha, it brings all requirements for a feature over.....
Guest
over 8 years ago
in Features
1
Will not implement