Development
Sort by:
Trending
Status:
Future consideration
Showing 136
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
Improve Jira importer project search
What is the challenge? In Aha! Develop, you can use the Jira importer extension to bring your existing records in Jira over to Aha! However, when you select the Jira importer on the prioritized backlog or sprint page, and you're presented with a d...
0
Future consideration
2
VOTE
2
VOTE
Add ability to turn off sprint velocity calculation in Aha! Develop
What is the challenge? Currently, a Team members' velocity is calculated from the work they have completed in the previous three sprints — and updates after every completed sprint. If they have not yet completed work in a sprint, their velocity is...
0
Future consideration
6
VOTE
Timer extension without capacity planning
What is the challenge? Our team would like a good idea of how long it takes us to complete types of work, however we do not want to fully dive into capacity planning. What is the impact? Using the timer is helpful, however the capacity planning el...
0
Future consideration
4
VOTE
Add risk filter to Aha! Develop boards
What is the challenge? You cannot filter a workflow board in Aha! Develop via a records delivery risk. What is the impact? It would be helpful to only display records that are at risk (i.e. because the record has no estimate or assignee) so that t...
0
Future consideration
1
VOTE
Sprint Planning: Ability to see multiple sprints at once
What is the challenge? As a product manager / scrum master role, I often do loose sprint planning projecting 3-5 sprints depending on the topics. Currently, I have to click into each sprint details to review the themes and notes, one at a time. Wh...
3
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
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
32
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
© 2025 Aha! Labs Inc.•All rights reserved