Option to not copy Requirements when Copying a Feature
What is the challenge? We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. What is the impact? This may create...
Lorena Connolly
2 months ago
in Features
1
Future consideration
What is the challenge? There is no easy way to send ideas to engineering to work on or keep the information in sync. What is the impact? Time spent copy and pasting data. Out-of-date information leading to confusion. Describe your idea Like the re...
As a user of Aha!, the amount white background I stare at is challenging. I adjust my monitors to reduce glare but it's still a lot. Could we have a dark theme to replace the white background as an option for users?
Greg Koeka
over 6 years ago
in Application
19
Future consideration
Allow users to modify Gantt charts like they can other roadmaps (e.g. group sections by product or on a custom field; show additional data). Want to visualize dependencies in roadmap form, but Gantt charts get cluttered quickly...
Danielle A
almost 3 years ago
in Roadmaps
3
Future consideration
301 Redirect feature to maintain a single link for time-sensitive documents like release notes
What is the challenge? Currently we'll have to change the links on the home page and create or manually redirect new links for our product/support teams to share release notes documents. This is especially problematic for teams that release freque...
Jeremy Bruno
4 months ago
in Knowledge base
0
Future consideration
Option to sync layout between idea portal and idea record
What is the challenge? Often when I am creating an ideas portal, I want the ideas form I set up in the portal to have the same fields show up automatically in the idea record. However, I currently need to also customize the idea record's layout in...
Max Robbins
5 months ago
in Ideas portal
1
Future consideration
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
Stephanie Lechner
3 months ago
in Jira
0
Planning to implement
Seamless Sync for Epics and Features Between Aha! and ADO when changing types
What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...
Associate the same custom field to more than one Aha record type
I've seen this mentioned a few places, but the Aha! staff seems to keep deferring to custom tables as being the answer, which isn't the need. When I create a custom field - let's say the customer's name or the segment impacted - I want to add it t...
Karie Kelly
over 3 years ago
in Account settings
6
Future consideration
Allow me to create a batch of individual to-dos or work requests
Who would benefit? Teams with large deployments who make heavy use of to-dos and work requests to track cross-functional work What impact would it make? Today, if I need to assign a to-do or work request to a large number of recipients, I have two...
Reilly O'Connor
11 months ago
in To-dos
0
Future consideration