All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5835
1
VOTE
Show features and master features linked with an initiative under the roll-up initiative as well
We use the roll-up initiative feature a lot at the line level and the initiatives at the product level. So all the features and master featured are linked to the initiatives but when we look at the roll-up initiatives, we are not able to see them ...
0
Future consideration
1
VOTE
Allow user to filter History to specific events
As a user, I need to be able to see the progression of date changes. I am unable to easily track changes to a specific field. I would like to be able to filter my history of an initiative to a specific event, such as End Date change.
0
Future consideration
1
VOTE
1
VOTE
Disable specific pages if not in main menu
We’ve got users landing on pages that have been disabled on their main menu when they navigate between workspaces. This causes some issues when rolling out Aha widely as an ‘intuitive’ self serviceable tool. An example is: Going to a workspace def...
0
Future consideration
1
VOTE
Use record colours in custom roadmaps
We can use Customize Style to change the colours of bars in Custom Roadmaps, but this requires us to individually set the colour for each item. This is painful when you have multiple roadmap reports and are trying to keep things consistent. In my ...
0
Future consideration
1
VOTE
Make Notes, available as a relationship custom field
We use notes to capture information related to the EPIC. While there are other custom fields that can be added natively to an EPICS's layout Notes is not one. The only way I've seen to attach a NOTE to an EPIC is making it RELATED. The issue with ...
0
Future consideration
1
VOTE
2
VOTE
Don't fail TFS Integration when attached file is too large
When a file has been uploaded to aha that is larger than the maximum file size,then integrate without the file in TFS, adding a note indicating this. This will allow the team to collborate on the TFS items without having to delete the file.
0
Future consideration
1
VOTE
Addition of one or more custom field in the requirement section within the Features
Since Bugs are not 'first class' entities in Aha and the suggested workaround is to map requirements with bugs in JIRA, we have done that and use a custom field of type in requirements which has the value of bug and story. However, when we open a ...
0
Future consideration
1
VOTE
© 2025 Aha! Labs Inc.•All rights reserved