All ideas
Sort by:
Trending
Status:
Showing 9094
7
VOTE
Allow "Reviewers" to set up an email schedule for saved views
Currently to schedule email delivery of saved views, you must be: The creator of the report AND A user with at least owner or contributor permissions. The #2 condition is because a report's settings could allow for sharing views as a webpage inste...
0
Future consideration
10
VOTE
Requirements capacity planning
We have users stories mapped to requirements in Aha!. When viewing the capacity planning at a requirement level it uses the feature level start and end date, we want to see the start and end date of the requirement (Story). Also related to this in...
0
Future consideration
44
VOTE
1
VOTE
Simplify the process of adding an existing record to the prioritization view
What is the challenge? The prioritization view is a great tool for scoring and ranking important work. Adding new records to this view is straightforward with a single button but adding already existing record is not easy. You need to filter or se...
0
Future consideration
1
VOTE
Create record from notification
What is the challenge? Users may need to take action based on notifications, but manually creating related records can be time-consuming What is the impact? Saves time by streamlining record creation directly from notifications Describe your idea ...
0
Future consideration
1
VOTE
Ability to sync Jira's "Team" bidirectionally
What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
0
Planning to implement
1
VOTE
1
VOTE
Issue Count Limit for Unranked Epics (Prioritization View)
What is the challenge? We frequently run into issues with the epic prioritization view. On a workspace line level, we have more than 100 unranked epics across 3-4 workspaces. Whenever we run into this issue, the view does not even show the workspa...
0
Future consideration
4
VOTE
Enhance text editor functionality
What is the challenge? We want to enhance our presentation style to be more colorful and the current text editor has limitations. This would be used throughout Aha in all applications. What is the impact? Better experience reading documentation by...
0
Future consideration
14
VOTE
Jira integration user name
In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved