ADD A NEW IDEA

Epic

Showing 157 of 8985

Multi-line text editing in Feature/Master Feature titles

When editing the titles of master features (or I assume it applies to any item like features, initiatives, releases, etc), the text editor should display multiple lines instead of just one. For long titles, the one-line display results in having t...
Guest over 5 years ago in Epic 0 Already exists

Additional time fields for customizing record cards

I would like to be able to have the option to add the original estimate, remaining estimate, and logged time fields to my feature and master feature cards (just like how I can pull them into a pivot table). It is helpful to see the original estima...
Guest over 5 years ago in Epic 1 Future consideration

Sharing Master Features between Products

We deliver customer solutions on top of our base product which often drive the development of (future) features in our base product. Because we have to manage these features separately as part of delivery of this customer "product", we then find w...
Guest over 5 years ago in Epic 0 Already exists

Expand Parking Lot field

As a Product manager, I work with my backlog in the parking lot. I would like to be able to expand the Parking Lot field to full screen or to at leas 2/3 of the screen in order to have a better view of my work. This is because, I work with differe...
Guest almost 3 years ago in Epic 0 Future consideration

Linking features to more than one master feature

I have a solution A which is made up of features X and Y from products B and C respectively. However, X and Y may also be features in solution B. With the recent update, you’re able to view master features along with features on the feature boar...
Guest almost 6 years ago in Epic 0 Will not implement

make data from a related record available as a field

currently a related record is only available for reporting as a link, which cannot be used for filters, pivots or sorting. This request asks to make information from the related record to be available as a field (custom or otherwise) so that it ca...
Frank Salvo about 3 years ago in Epic 0 Future consideration

Visually represent the size of a feature with larger or smaller cards

In Aha, it's difficult to represent the relative effort required for different master features and features. Time is not the only consideration. For example, so features have dependencies that while not requiring heavy effort, will effect the dura...
Nate Dunlevy about 6 years ago in Epic 1 Unlikely to implement

How about inline comments on a requirement DON'T get deleted when that text is altered or removed... that would be great.

Just lost a lot of context and work items that were in comments when an edit was made that removed content from the requirement. This is unacceptable and frustrating. How is it that they aren't stored in the comments section, or the history... the...
Guest about 3 years ago in Epic 1 Already exists

Restrict access to bulk actions

We have 20+ people in Contributor role working on the same Product. All of them have by design access to bulk actions and can inadvertably bulk delete all of the hundreds of items that we have in Aha!. We want to somehow restrict access to bulk ac...
Guest about 6 years ago in Epic 0 Unlikely to implement

Have more record types as primary record in dependency reports

In the primary record you can only select one record type, and hence visualize only fields from that record. However, you can add filters on other record types. Would be more convenient to also be able to visualize and sort these in the primary re...
Kristof Dewulf about 3 years ago in Dependencies / Epic 0 Future consideration