Skip to Main Content


Showing 1171

Allow users to add existing features to User story maps.

Who would benefit? Users who create in both places What impact would it make? Helps PMs tell the story better for previously defined work How should it work? Steps User on User story maps selects map to which they wish to add the feature (new) use...
Guest 4 months ago in Features 1 Already exists

Bulk Copy Features

I have a segment of 8 features in one release I want to copy into another release (we use these as tasks that we frequently clone into new releases. But I can't do this currently without:1. Copying the entire release (all features) 2. Deleting 90...
Guest almost 7 years ago in Features 3 Future consideration

Include Related Feature Items in Automation Rules

We have a use case where we want to automatically send a link to the idea associated with a feature to Jira. We thought the way to accomplish this would be to include a custom field on the feature that we then populate through an automation rule, ...
Jerimiah Rudden over 2 years ago in Features 0 Future consideration

Change Log per field

Who would benefit? All Aha! users What impact would it make? Easy to track changes on key important fields How should it work? Able to create reports to show changes per field, which could help the auditing process
Edgar Holguin 4 months ago in Features 0 Future consideration

Decouple requirements from Features

Who would benefit? Users of AHA What impact would it make? Allow for my dynamics way of using AHA How should it work? One should be able to create a requirement (or whatever you want to name it) without being forced to link it to a feature. At Roc...
Guest 8 months ago in Features 0 Unlikely to implement

Automation of related record (Feature) updates the "parent" Record (Feature)

The work request option is great and one of the main functions we utilize to connect dependent work across programs. The only issue we see with this is that the parent record, in our case a feature, does not get updated when the "related" record i...
Danielle Martinez over 1 year ago in Features 4 Future consideration

Aha! Automation Needs Improvement

I have a mandatory custom field in Aha! Feature’s form and I would like the field to be non-editable once the release is approved through fixed workflow statuses, so that people could not make any changes there and any exception changes should go ...
Ankush Kumar about 1 year ago in Features 1 Future consideration

Bring back common text editor buttons

Why were common editor buttons hidden under drop-downs ??? This is an unnecessary change and it's very inconvenient when working on features and requirements.
Guest about 1 year ago in Features / Notes 1 Future consideration

Capacity management cross releases

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 effort"), the original estima...
Daniel Pokrývka over 5 years ago in Features 2 Future consideration

Allow more than one "Assigned to" on Feature cards

We have feature cards that need to be assigned to more than one person
Carolee Snarr over 3 years ago in Features 0 Future consideration