Features

Oftentimes it's the same team intaking and executing on work, so we'd like the option to have an assignee for an Idea be able to cross over to a Feature upon conversion.

As a product manager I want to be notified when a feature that is a dependency of one I own is modified. Specifically if the deliverable dates shift and impact my feature. This is currently possible by adding myself as a watcher to the dependent...

What is the challenge? The prioritization report cannot display strategy fields tied to multiple records (like goals, objectives, and key results). What is the impact? Goals, objectives and key results are vital reference points when determining a...

We have feature cards that need to be assigned to more than one person

When features aren't completed or when you're making of list of say UX enhancements that you don't want to loose track of in a dummy feature in the parking lot, I'd like to be able to drag them into a new feature I create in the upcoming Release. ...

As an Aha! user, when I filter based on User ("assigned to", "created by", etc.), I should be able to choose "Current User" as an option. This way, when I save and share a View, the results are dynamic and update based on the signed in User. For e...

When using a scorecard, given the way users think about scoring, rather than using a numeric scale, I would like to be able to assign text [as the slider element] and have this equate to set values As an example Technical Feasbility would have 3 v...

What is the challenge? We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. What is the impact? This may create...

Who would benefit? All team members as we use the velocity view for assignments and epic prioritization. What impact would it make? The view would be more realistic and not padded How should it work? Aha calculates used and available capacity for ...

We would like to remove "requirement" from our custom feature layout as this adds "too many layers" to the work. We want to utilize "to do" only within our workspace.