In general our portfolio workflow involves us managing our backlog in Aha, but then creating a physical board that has all the current and upcoming features on a standup board where all of our team members can gather and discuss. Working only onli...
Guest
over 8 years ago
in Features
5
Unlikely to implement
Put current product at top when choosing initiative or goal for a feature
The initiatives drop-down contains initiatives from all products, sorted alphabetically. I think the initiatives from current product should appear in the menu first.
Chris Waters
about 10 years ago
in Features
3
Already exists
Allow re-ranking requirements on a feature by status
As I work through the requirements on a large feature, I find it useful to keep them sorted by status, so I can have a focused group of items that still need my attention. It would be nice to automate this sorting via a rerank button, similar to t...
Zach Schneider
almost 7 years ago
in Features
0
Future consideration
Include custom requirements fields in CSV upload into Aha
We have several teams who use the Aha CSV uploader to help cut down on manual entry time for recurring projects. It would be helpful if they were able to add custom requirements fields to the features uploader. As our company begins to scale, the ...
Guest
over 7 years ago
in Features
2
Unlikely to implement
Sometimes I use Features Board to discuss with internal stakeholders, and I don't feel comfortable showing internal release date there. External normally has some buffer and more generic (like a quarter of the year, when I am planning to release)....
Pablo Perez
about 8 years ago
in Features
6
Unlikely to implement
Alert when moving a feature from one product to another
We love Aha! for it's flexibility. However, it would be great to configure something platform wide (our platform). We would love to be able to have warnings if the user tries to move a feature from one product to another. This happens to us (accid...
Guest
over 9 years ago
in Features
1
Will not implement
Automation of feature to another release based on custom field
Who would benefit? Product Management Team What impact would it make? Ability to cut down on manual work, reducing mistakes and time spent on administrative work How should it work? Under automations, be able to set a rule as such: When a feature ...
Danielle Martinez
about 1 year ago
in Features
2
Future consideration
In the old Aha! design there was an option on a feature to expand all the requirements. This was great for quickly showing all the links to Jira. Could you bring this option back?
Kelly Sebes
about 4 years ago
in Features
0
Future consideration
What: Hide Tabs on new look/feel experience for Feature Cards Why: Some information is more prevalent now in the view (e.g. Change Log) and may add confusion for our teams as we follow a different process for change management.
Guest
about 4 years ago
in Features
4
Future consideration
The trouble is that when you plan a feature into release R1 with capacity C1, it is not a super rare situation when after execution of that release (when collecting data from requirements as "work done" and "remaining effo...
Daniel Pokrývka
over 5 years ago
in Features
2
Future consideration