All ideas
Sort by:
Trending
Filter by:
Status
Showing 9061 of 9061
2
VOTE
Add a Product Architecture section
The workspace needs a more permanent architecture planning section. The Draw.io functions within notes section are very helpful but are attached to features and releases, which tend to be transient in nature. An architecture workspace would be mor...
0
Unlikely to implement
3
VOTE
Allow email alias in accounts for replying to comments
We use multiple email addresses. We get Aha! comments and updates sent to one address, the user account email, but when replying we have to manually set the 'send from' address (in gmail) register the comment in the Aha system. It would be really ...
2
Unlikely to implement
1
VOTE
POST for /api/v1/products/:product_id/idea_categories
We want the Categories that an Idea is assigned to, to be 1:1 with our Components from Jira. We could utilize the JIRA Rest API and the AHA Rest API to keep these two lists in sync, however the AHA API only has a GET protocol available and lacks a...
0
Future consideration
1
VOTE
Add epic, feature, release semester
You can include an 'Epic quarter', 'Feature Quarter' or 'Release Quarter' in list reports and roadmaps that Aha! calculates from the release date of the release. However our client facing roadmaps are produced by semester, it would be great to hav...
0
Future consideration
1
VOTE
Link from Ideas Roadmap to Ideas Portal
WHen my users have sent an idea into the AHA ideas portal, and I have promoted it into an EPIC, the user would like to be able to see, in what release/EPIC within the AHA roadmap the idea is going to be shipped. It could be convenient to have a li...
0
Future consideration
2
VOTE
Ability to sort results using REST API
When retrieving lists of items with the REST API it would be nice to be able to sort by a field. For example, if sorting by last updated date was supported, integrations that query items (using pagination) could stop once they encountered items th...
1
Already exists
1
VOTE
3
VOTE
Allow for integration via OAuth 2.0 Service Accounts
Ask: Support OAuth 2.0 Service Accounts for auth on the Aha! API
Background: We use SSO (Okta) for user authentication (Aha! doesn't know about passwords by design). We also have a set of scheduled tasks (scripts) that query the Aha! API, summariz...
1
Already exists
3
VOTE
Notifications for changes made to to-dos (Picture Included)
This feature would simply put a notification on the requirements line in all panels of Aha!. These notification will include:
New Comment
This will show that a To-do has a new Comment.
To-dos Completed Indicator.
Will show the # of to-dos com...
0
Unlikely to implement
2
VOTE
A way to retrieve all the fields, including custom fields, and metadata for an item type (eg. Feature) using REST.
Field information would ideally include the type of the field (string, number, drop down, etc.), and properties such as if it is a required field or read only field. This would allow the integration to know what fields are available when creating,...
1
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved