Skip to Main Content
ADD A NEW IDEA

Features

Showing 728

Prioritization Report - Allow more than one level of record structure

On the feature prioritization report, under the “edit columns” option, when I select “+ Add records related to this epic” it returns a blank list. I’d like to add initiatives to this list. This is needed when Epics are linked to Initiatives, but n...
Evan Hollohan 3 days ago in Features 0 Future consideration

To add possibility to set up automation rule based on delivery risks flag changed automatically (right now only manual change is taken into account)

Who would benefit? Aha users What impact would it make? It will be possible to automate the process of filling up the needed field on initiative level based on automatic change of value of delivery risks flag field on feature (epic) level How shou...
Daryna Podchakha 5 days ago in Features 0 Future consideration

Easily add feature to Develop team's backlog from Roadmaps

Who would benefit? PMs/POs using Aha! Develop What impact would it make? Ensure that a prioritized feature actually show up in their team's backlog How should it work? Provide a button/drop-down in Roadmaps to easily add feature to team's backlog ...
Nathaniel Collum 18 days ago in Features 0 Future consideration

Make it easy to prioritize a body of work's child records

Who would benefit? Teams who need to ensure clear prioritization on the subtasks within a body of work. What impact would it make? Right now, the only way to filter, for example, the features prioritization page to a specific body of work, is usin...
Reilly O'Connor about 1 month ago in Features 0 Future consideration
122 VOTE

Require fields by status

I have certain fields that need to be filled in before moving to the next status in my workflow. The data for these fields is not known in the previous statuses, so it can't be set as a required field before the record reaches a certain status. Th...
Bonnie Trei over 3 years ago in Features 10 Future consideration

Create "Requirement Field" as new custom field type

Who would benefit? Any company that creates platform products What impact would it make? It would allow to connect items across workspaces that belong to difference levels. In our case we can use it to determine the influence of a feature or a req...
Alessandro Alfano 12 days ago in Features 0 Future consideration

Priority limit line on subsequent pages of Prioritization view

Love the new prioritization lines introduced last week. However, they can only be placed on the first page. We have a need to also place them on the subsequent pages, as we have that many features to keep track of. We're hoping to use these to als...
Guest 7 months ago in Features 2 Future consideration

Ability to Configure Default View (Drawer / Details) for Records

Who would benefit? All Aha users What impact would it make? Provide consistent and optionable record viewing experience to users. How should it work? Provide the Drawer and Details view options in personal setting per user preference on viewing ...
Hank Liu 15 days ago in Features 0 Future consideration

Change feature rank standard field name

Who would benefit? User utilizing the prioritization page for features, and other record types What impact would it make? Reduce confusion on feature rank vs prioritization rank How should it work? Change the name of the standard field Feature ran...
Peter Whisenant 30 days ago in Features 0 Future consideration

Nest or group to-do items together

Who would benefit? PMs, Product Ops, docs team, What impact would it make? Easier to use and navigate to-do lists within discrete phases How should it work? I'd like to be able to nest or group to-do checklist items under a higher-level checklist ...
M K about 1 month ago in Features 0 Future consideration