Development
Sort by:
Trending
Status:
Future consideration
Showing 133
1
VOTE
Could we add a coffee cup during the Planning Poker?
What is the challenge? Team Members sometimes wants to have more time to discuss the issues in poker planning, but there is no way to communicate back What is the impact? People are using big numbers in the planning pokers to represent the issues ...
0
Future consideration
9
VOTE
Kanban - Workflow Heat Map
What is the challenge? When running an effective Kanban system it's important to know where the bottlenecks in the process are. What is the impact? Currently I have to export the data to a spreadsheet to work out the problem stages. Describe your ...
0
Future consideration
6
VOTE
Allow multiple assignees on Features and requirements
What is the challenge? Many teams have more than 1 person working on something. For example a couple of devs and a tester could be working on a complicated feature together. We currently can't do that. Additionally for performance reviews it's nic...
0
Future consideration
1
VOTE
2
VOTE
AI assistant to help me break down epics / features
What is the challenge? I spend a lot of time working on the details of an epic or a feature. Linking research, ideas, corporate initiatives. Then I send the work to a team or a product owner for them to breakdown into smaller units of work. Often ...
0
Future consideration
2
VOTE
Epic/Feature boards using custom fields than versions
What is the challenge? Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field...
0
Future consideration
82
VOTE
30
VOTE
Allow automations to run on any custom field
Not just the fields present in your epic/release/feature/idea template. I have flows for each of these record types that add new fields for input later on and would like to run automations on them, but can't unless I add them to the template used ...
1
Future consideration
3
VOTE
Restrict ability to open or close sprints
What is the challenge? On some teams, only certain team members are allowed to start or close a sprint. Currently anyone with contributor access can open or close a sprint. What is the impact? Sprints are open or closed in error. Describe your ide...
1
Future consideration
4
VOTE
Allow team members with Aha! Develop permissions to be able to add and update research notes on features from Aha! Roadmaps
What is the challenge? When features are assigned to a team in Aha! Develop, team members that don't have roadmap permissions can not add additional documentation to the research tab as it attempts to add the notes to the Roadmap level Knowledge B...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved