All ideas
Sort by:
Trending
Status:
Showing 9037
1
VOTE
Allow Idea viewer to update proxy votes (not raised by you)
As it currently stands Idea viewers are not able to update votes, which were not raised by them. There are multiple reasons why the viewer may want to update existing votes: 1) reflect the latest severity / impact (e.g. downgrade / upgrade) 2) mod...
0
Future consideration
1
VOTE
Disable idea email notifications by status
We archive ideas that are over a year old and have not received any votes to simplify our internal research. In most cases, these Ideas are already marked Will Not Do, so our customers don't need another notification that we're still not doing it....
2
Already exists
2
VOTE
Advanced Integration with Zapier
I was trying to do an integration between Freshdesk and Aha, and since there is no direct integration, I used Zapier, however, the fields available at Zapier are just the idea title and description, all the custom fields I have on Aha's ideas are ...
0
Future consideration
3
VOTE
1
VOTE
Manage Users admins shouldn't be allowed to change the admin roles for themselves or other users
People in our organization are given the Manage Users admin role in order to manage the licenses associated to paid seats. However, the Manage Users admins are able to assign additional administrative privileges to themselves & other users. Am...
3
Future consideration
1
VOTE
Prevent users of adding comments and/or to-dos in custom templates
Users get confused and add comments about the feature in the requirement card. Same happens with to-do. As a consequence, the progress is calculated wrong and the reports don’t show the information you want, like “last comment”.
0
Future consideration
1
VOTE
Provide help with consequences of merging custom fields
The Aha! KB article on merging and converting custom fields explains that there are implications for integrations and reports when merging fields. Specifically: If an integration included the old custom field, you will need to update the field map...
0
Future consideration
2
VOTE
Capacity planning by half (instead of by month)
At the initiative level, we plan 6-12 months into the upcoming fiscal year, by half. We estimate team capacity (high-level t-shirt sizing) by 1H and 2H. Our goal is to know the right scope moving forward and balance our engineering capacity for 1H...
0
Future consideration
2
VOTE
Mass Update of Workspace custom fields
As a user, I need the ability to do a mass update on Workspace custom fields so that we can utilize those fields for reporting. All of our products have specific business programs and business segments so we created a custom field to capture progr...
0
Future consideration
4
VOTE
Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited
In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved