Features
Sort by:
Trending
Status:
Showing 1189
1
VOTE
2
VOTE
Workspace owners should be able to edit their scorecard
As a workspace owner, you are not currently able to edit your scorecard. This means you need to coordinate with the Aha! admin in order to make those changes. The workspace owner should be able to have that editability in order to control what is ...
1
Future consideration
2
VOTE
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
2
VOTE
Additive Inheriting of workflow approval groups
I want to set up approval groups where a certain set of individuals have approval across a whole product line while other groups have approval only for specific product workspaces within that line. I've just discovered that inheritance for workflo...
1
Future consideration
3
VOTE
More granular capacity definition for teams
I would like to be able to better define the capacity of my teams, i.e. define a work schedule for each member and have them rolled up into the team, rather than enter manually at the team level or get 8 hours by default define holiday time for ea...
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
Future consideration
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
2
VOTE
Allow One to Many custom table relationship field to be more flexible
When creating records in a custom table that are linked to another record through the One to Many relationship field it forces the parent record to prepend to the name of the table record. If this record is then utilized elsewhere the name is elon...
0
Future consideration
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
© 2024 Aha! Labs Inc.•All rights reserved