Application

Showing 7751

Change Master Feature Prefix

The Prefix for all Master Features is 'E', this is a suggestion to change this globally to M to align with the default terminology. EG PRODUCT-E-123 should be PRODUCT-M-123 instead.

Guest over 5 years ago in Epic 1 Unlikely to implement

1 VOTE

Support Cost as an Estimate for Capacity Planning

Our business strategy team receives cost estimates instead of story points and time. Since story points and hourly pay rate can vary across different teams working on the same features, being able to see how cost estimates roll up from features to...

Lan Nguyen almost 2 years ago in Capacity planning 2 Already exists

2 VOTE

Allow for null Release Date

Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...

Brendan G almost 4 years ago in Releases 0 Future consideration

2 VOTE

Allow child releases for a master release to retain unique names

There are instances where multiple releases exist within the same product workspace that are separated intentionally for visual management. Creating a rollup release causes the children to inherit the parents name, but it would be useful for the c...

Ronnie Merkel almost 4 years ago in Releases 0 Future consideration

2 VOTE

Have linked releases to goals and initiatives only show work related to that container

Currently the linked releases to an initiative or goal, show all complete and pending stories for the release. If a release is not 1:1 with the initiative or goal, those items are showing work that is not related which gives a false perception to ...

Ronnie Merkel almost 4 years ago in Strategy 0 Future consideration

2 VOTE

Issue with Strategy Roadmap display

When I have initiative planned say for example, 2 releases, first one in the 2nd qtr, 2021 and 2nd one in 4th quarter, 2021, strategic roadmap doesn't reflect it correctly. It shows continues bar going from April 1st, 2021 until end of the year gi...

Ram Dhurjati almost 4 years ago in Roadmaps 0 Unlikely to implement

2 VOTE

Parking lot features

This is not an idea but more of a missed Aha! functionality or bug. When we create features and put them in parking lot with initiatives assigned them, these features are showing up in my roadmap (strategy roadmap) in spite me selecting "hide park...

Ram Dhurjati almost 4 years ago in Features 1 Future consideration

5 VOTE

Add Development Lead as a Role

We would like Development Leads to be able to update status on features & requirements once they have left the planning phase. Ideally, the Dev Lead could update status & add comments once the feature/req gets into the "In Development" phase.

Matt Lavallee over 9 years ago in Account settings 7 Will not implement

4 VOTE

Add Ability to Filter in Feature Board View on Estimated Effort Points Field

We often sort our work based on what has been estimated with effort points and what hasn't. We would love to be able to use the Board View and filter on Estimated Effort Points so that we can see at a glance what needs effort points still.

Danette Colin over 7 years ago in My work 0 Already exists

1 VOTE

Support PKCE based Auth Code requests for OIDC SSO portals

We request that Aha! enhance their security posture as it relates to authentication and follow industry recommendations: https://oauth.net/2/pkce/ “PKCE is not a replacement for a client secret, and PKCE is recommended even if a client is using a ...

Joe Granville almost 2 years ago in Account settings 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY