All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5905
1
VOTE
Add user first name and last name fields to Get User API response
Currently Aha stores user first and last names. In the get user and list users REST API response objects, those fields are combined into one field: name. So John and Doe just get returned as John Doe. This causes problems when you have many differ...
0
Future consideration
1
VOTE
Ability to show more release details on the feature board
In the feature board view, the top of each release column shows very limited information today. Just release name, release date, and capacity. It would be useful to show more information about a particular release at the top of each release column...
0
Future consideration
2
VOTE
Develop an OSLC REST based connector for Aha!
We need to link Aha! Roadmap items to other items in Sparx EA (OSLC compliant) using ArchiMate 3.1 and an OSLC connector for Aha! will enable us to do that. This connector will also enable us to link Sparx EA ArchiMate 3.1 model elements such as s...
0
Future consideration
2
VOTE
New section under Strategy or Info for definitions/product functions.
Our Product has multiple functions/modules. With each module there are some terminologies and concepts that need to be defined. I can use notes to create a document but that that can get messy really quick. I see this area working similar to how P...
0
Future consideration
4
VOTE
Configure Filters - Change Arrangement of Fields
It would be useful to be able to change the order of filter fields when configuring filters. After adding filter criteria, especially over time, it can make sense to put the fields in a certain logical order. Having the ability to drag-n-drop the ...
0
Future consideration
2
VOTE
Block default customization from being modified
Anyone with customization permissions can modify the Default workflows, scorecards, time frames, etc. Without removing the option to set new default, why not blocking the default from being modified? this will allow an encourage users with the rig...
0
Future consideration
2
VOTE
Don't automatically open links in notes/descriptions in a new tab
When you try to open a link from a note/description in a new tab, some javascript automatically opens the link in a new tab and changes the focus to it. Opening a link in a new tab should be done in the background, like when done with the middle m...
0
Future consideration
4
VOTE
Link user stories (requirements) in JIRA when under the same epic (feature)
We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
2
Future consideration
1
VOTE
Allow Timeframe to be used for filtering in Worksheet fields
As part of our maturity review we want to quickly understand if a particular workspace has planned their Initiatives and Goals in the current Timeframe (e.g. this year). To do this we'd like to create a worksheet on the workspace object, but the f...
0
Future consideration
2
VOTE
Allow each team to provide an independent set of tags on a feature
Looking at the tags field on a develop feature, it inherits all of the tags from my main roadmaps workspace. This isn't the behaviour I'd expect, I would expect a develop team to have its own unique set of tags of primary relevance to them. In pla...
1
Future consideration