Features

There are times where we have multiple people working on a story, either due to investigating a spike or pair-programming. It would be nice to be able to assign a feature to more than one person at the same time.

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...

It would be nice to be able to label things on cards in the board view. For example, I have multiple scorecards (one for product features and one for technical debt items I'm tracking in the same backlog). It's not easy to tell what the number is ...

We use AHA across multiple sub-businesses. Our sub-business relies on capabilities delivered by another sub-business. It'd be much more efficient to make sure dependencies are properly mapped if I could make multiple features depend on another fea...

As a user I want the ability to sort related item table rows by Rank so that the highest priority related item is first in the list

we sometimes add user stories to a feature after other ones have been completed, for example feature is to deliver a piece of functionality and we create a spike, and then that may get closed before we add all the other user stories needed to comp...

What is the challenge? Trying to make a bunch of changes in parking lot items, and the slide-in covers them, so you have to manually close the slide-in before you can click another story What is the impact? Wasted effort/time when working on parki...

In this view it shows features alpha ordered. It would be helpful to see what releases they are in or by status.

What is the challenge? When using FeatureTags as Filter it does no longer show the selected Features Tags on Top like for selected Releases What is the impact? When selecting multiple Features Tags it makes it very labor intensive to de-select the...

I would like to be able to have my QA team track bugs against a Requirement. It would enable better visibility into the probability of a specific feature / requirement making it in to a projected Release (or the likelihood of the release slipping)...