Delivery
Sort by:
Trending
Status:
Likely to implement
Showing 175
8
VOTE
Ability to see requirements assigned to Team from Roadmaps on Team timeline
What is the challenge?
Teams are usually assigned requirements from roadmaps, not features. This means they get no advantage from using the timeline board as the board requires a feature to be assigned to the team to then nest the requirements
...
0
Future consideration
9
VOTE
The ability to collapse\expand all on the Teamwork board and Backlog management board
What is the challenge?
When there is a large number of groups on the Teamwork board or Backlog management board, you have to manually collapse every group. For example, the product work on the backlog management board may have 30 releases, each ...
3
Likely to implement
6
VOTE
Support Team and Workspace automation rules with "same as" actions for any sprint
What is the challenge?
Currently, automation rules with sprints only allow you to set actions that are based on the current sprint, not any sprint.
You also cannot set "same as" action rules for related records.
This means if you'd like require...
2
Future consideration
20
VOTE
Add standard date fields to requirements in Aha! Teamwork
What is the challenge?
The marketing team is moving into Aha! Teamwork. We are excited to gain more visibility into requirements by tracking them on the workflow board.
Much of our work is date driven. Think GtMs, blogs, social posts, SBs. This ...
1
Future consideration
1
VOTE
Add count of items to group on Teamwork Workflow board when collapsed
What is the challenge?
The ability to collapse all on the Teamwork workspace is a great new addition. But it would be very helpful to see a count of items in the group so we no which groups to expand
What is the impact?
We can now easily c...
0
Future consideration
2
VOTE
Activity type to cycle & lead time report
What is the challenge?
The Cycle and lead time report takes broad strokes at how much time it takes for the team to complete work but doesn't allow us to drill into types of work
What is the impact?
We aren't getting data to help inform fu...
0
Likely to implement
4
VOTE
Rearrange Develop Teams within a Team Line
What is the challenge?
Currently, you cannot move the Team order around within a Team line as you can with Workspaces in a hierarchy. When setting up PI's I'd like to be able to rearrange the Team order on my Program Board
What is the impact...
0
Future consideration
5
VOTE
Support Aha! Roadmaps workspace to Aha! Develop Team bidirectional status mapping
What is the challenge?
Currently, you can only map Aha! Develop Team status to Aha! Roadmaps workspace status, not vice-versa.
What is the impact?
Relevant status updates made in Aha! Roadmaps workspace cannot continue a workflow in an Aha...
0
Future consideration
3
VOTE
Nested records across workspaces
What is the challenge?
Two separate teams might need to track one piece of work assigned to one team but have visibility into that work on their own workspaces. Currently, two records need to be created, one on each workspace, and moved along th...
0
Future consideration
2
VOTE
Ability to collect feedback from users via a form/poll within your Aha! account
What is the challenge?
A way to consistently gather usability feedback from users
What is the impact?
Users share usability challenges in email, IMs or sometimes in meetings (Data is inconsistent)
Describe your idea
A feature that ca...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved