All ideas
Sort by:
Trending
Status:
Showing 8967
3
VOTE
3
VOTE
4
VOTE
Requesting access to a edit a document results in an email to the 'Owner', we would like to be able to send the notification to the Idea Custom Field: 'Product Manager'
Who would benefit? Product Managers What impact would it make? The Notification path would be modified to the appropriate Product Manager since we do not use 'Owner' notifications in our Enterprise How should it work? When a aha User requests edit...
0
Future consideration
3
VOTE
Prioritization Report - Allow more than one level of record structure
On the feature prioritization report, under the “edit columns” option, when I select “+ Add records related to this epic” it returns a blank list. I’d like to add initiatives to this list. This is needed when Epics are linked to Initiatives, but n...
0
Future consideration
3
VOTE
Provide a setting to add new Epics and Features to the Epic/Feature roadmap without user action
We have a very large Epics roadmap, new Epics are added to releases by the team very frequently. We want a setting that shows all new records added to releases in the roadmap shown in webpages and presentations. It is not reasonable for someone to...
0
Future consideration
6
VOTE
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
0
Future consideration
12
VOTE
Ability to report on usage and references to saved views to aid in cleanup
As longtime Aha users we have accumulated hundreds of saved views, presentations, and dashboards. It would be ideal to be able to identify old, outdated saved views that are no longer being used or referenced so we can surgically cleanup this coll...
1
Future consideration
26
VOTE
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
0
Future consideration
18
VOTE
Allow importing of portal comments or toggle internal to portal
Currently Aha! ideas import via CSV puts comments as internal so they are not viewable by portal users within the portal. We are consolidating all our different methods of ideas gathering to just use Aha idea portals and have a lot of data to inpu...
4
Future consideration
5
VOTE
Add delivery risk check for connecting work to strategy
We need to ensure that all of the work we deliver is driving our overall product strategy. Create a new delivery risk indicator that is triggered when a record does not roll up to a larger part of the plan (e.g. feature doesn't have an epic set, e...
0
Future consideration