Delivery
Sort by:
Trending
Status:
Future consideration
Showing 133
1
VOTE
Count the number of times a feature or requirement goes into a status
What is the challenge?
For development cycles (Aha Develop), it's important to know how many times a feature is returned to development as a means to determine if a developer is doing proper unit testing or adhering to acceptance criteria.
W...
0
Future consideration
2
VOTE
Add AI to the develop side in order to analyze backlogs, sprints, features etc.
What is the challenge? Would like to use AI to help find inconsistencies with backlog items, or analyze the efficiencies/inefficiencies of sprints What is the impact? AI has been added in several places in Aha! but not over in Develop. Describe yo...
3
Future consideration
5
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
2
VOTE
Filter using Feature location in Aha! Develop
What is the challenge? Currently, you cannot filter records within Aha! Develop screens, like the parking lot by the feature location field (backlog management, sprint, workflow board etc.) What is the impact? This would allow teams to filter the ...
0
Future consideration
1
VOTE
Automation: require field based custom field option
What is the challenge? During the lifecycle of an Epic, we have fields that when a certain option is selected, another field should be required. What is the impact? Data is not complete so reporting is incorrect. We have features that that when a ...
0
Future consideration
2
VOTE
Allow exit criteria for each status in a workflow board to help users understand when they should progress an item to the next status.
What is the challenge? this information is currently stored outside of the tool making it unlikely for users to follow company guidance What is the impact? teams are progressing items that are not ready. we are building exceptions reports to fulfi...
1
Future consideration
10
VOTE
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
6
VOTE
Enable automations to work with custom "One to Many Relationship" tables
It would be great if we can have automation rules working with "One to Many" relationship type of custom tables. We use a custom table to track risks in issues in multiple record type and would be great to add new records based on a trigger at the...
0
Future consideration
10
VOTE
© 2024 Aha! Labs Inc.•All rights reserved