All ideas
Sort by:
Trending
Status:
Showing 9084
5
VOTE
7
VOTE
Specify which fields will and will not be copied when copying a Feature
What is the challenge? When a Feature is copied, any field that is filled in will automatically be copied over to the newly created Feature What is the impact? Although most of time this is ok, some fields are Read-Only and therefore cannot be cle...
1
Future consideration
1
VOTE
Ability to add automation to move a work item to a different release based upon a field
What is the challenge? There are times that certain records can move to a different release based upon the selection of a predefined choice field and do not require analysis and decisions. What is the impact? Inability to set up automation to do t...
0
Future consideration
1
VOTE
Shapes + templates layer over stick notes
What is the challenge? Shapes can interfere with the layers of sticky notes. It often happens that a shape will appear on top of sticky notes even when having been sent to the back, and having also sent the sticky notes to the front. The sticky no...
0
Likely to implement
1
VOTE
Show Total for Doughnut Charts
What is the challenge? When using Doughnut Charts you have to do math in your head to calculate the total items represented on the chart What is the impact? Data is not as usable for executive presentations as it could be Describe your idea In the...
0
Future consideration
1
VOTE
4
VOTE
Support custom Users field and other record type custom fields on the Now, Next, Later card layout
What is the challenge? Currently custom Users fields and other custom fields for records (i.e. Personas, Competitors, etc) cannot be added to the custom card layout on the Now, Next Later Roadmap What is the impact? Users cannot customize this vie...
0
Future consideration
4
VOTE
Prevent users from updating fields through bulk edit when set to "read only"
What is the challenge? A set of fields on various records (initiatives, epics and others) are used for financial reporting and should only be editable for a specific set of users. The fields are set as read only in their custom layouts, but can st...
0
Planning to implement
8
VOTE
Distinguish API key usage in history
We currently have two applications writing to Aha using 2 different api keys, but both under the same user. It would be great to have a way to distinguish which api-key is used in the history tab of a record. Currently it only shows the user so a ...
2
Future consideration
10
VOTE
"Owners" field in workspace reports
What is the challenge? It can be difficult for users to find the correct person to give them access to a workspace. What is the impact? Users will often ask the admin team for access to specific workspaces, instead of the workspace Owners. When th...
0
Planning to implement
© 2024 Aha! Labs Inc.•All rights reserved