Features
Sort by:
Trending
Status:
Showing 1197
4
VOTE
Version control for Features
When we believe a Feature is ready to be implemented, we want to assign the Feature description a version number so that everyone knows what version of the Feature description is being implemented. If the Feature description subsequently needs to ...
0
Future consideration
4
VOTE
4
VOTE
Changing font style and size on feature card
Some items on the feature card you would like to stand out more. Fields like status or team name (custom field) are preferably shown bigger on the feature card. The feature ID typically shown in the top left corner could be shown in small fontsize...
0
Future consideration
6
VOTE
Configurable relationships in the Dependency Map
I'm glad to see the dependency map feature appear. However, I notice it doesn't just show dependencies, it also shows "relates to" relationships. On the map, they are indistinguishable, which is confusing. It would be great if I could limit the ty...
0
Unlikely to implement
1
VOTE
Ability to update Requirement or other record fields based on a query
We use a series of standard Requirements for each feature flowing through the pipeline. Depending on the values in certain fields, some of those requirements are not applicable. Automation lets me change the value of the workflow status, for examp...
0
Future consideration
4
VOTE
Weighted Shortest Job First (WSFJ) Fields & Calculator For Initiatives, Master Features, Or Features
As more and more organizations embrace Scaled Agile Framework for Lean Enterprises (SAFe) as we did, the need to score and rank by the prioritization model WSFJ occurs everyday. Given we use Aha! for our Portfolio and Program level planning, ...
0
Already exists
6
VOTE
Ability to hide the feature prefix/code on Feature Roadmap and Presentation Export
On the Feature Roadmap, where it lists the features included in a release, each Feature's Prefix/Code (e.g. DEMO-22) is displayed. This takes up a lot of room unnecessarily and should be able to be hidden if it's irrelevant for the purpose of the ...
1
Already exists
4
VOTE
Agile Affinity Story Pointing for Features
We currently manage our work between the product manager/owner in Aha and transition to Jira for development and tracking is Agile/Scrum. We either print out the features as cards we can play with in a room, or we enter them into Excel or another ...
1
Unlikely to implement
5
VOTE
As a product manager, I want to be able to expose custom field data in my feature cards because I'm organized around custom fields and not the standard fields.
I have pieces of data that are very important to me and my business, but aren't part of the standard Aha fields that features come with. It's great that I can create custom fields, but now that I have and have months of data pushed into those fiel...
4
Already exists
1
VOTE
Changing the 'To Do' Label or Terminology
Issue: The ‘To Do’ is represented in two areas in a feature as 1) The ‘To Do’ and 2) ‘To Do – To Do Tab’. With that said, The duplicate terminology naming of ‘To Do Tab & the To Do’ is causing confusion issues with best practice adoption. Use ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved