All ideas
Sort by:
Recent
Status:
Future consideration
Showing 6183
1
VOTE
Important dates for the calendar view
My team is trying to become more deadline oriented and having the option to view our feature requests with their due dates AND our sprint schedule in the calendar view would be super helpful. Right now our sprint schedule lives in excel and person...
0
Future consideration
1
VOTE
Develop velocity and burndown report improvements
Improve the way the velocity report within Develop handles records that are re-estimated, added or removed during an active sprint. Specifically would like to see:- Ability to re-estimate a record after the sprint has started without any adverse i...
0
Future consideration
1
VOTE
Allow deletion of types and other data while still in use
There are several places in Aha! where we disallow a user action because an object is in use. For example, users can't delete a custom type while records are using it. We already have an elegant solution in place for this when changing from one wo...
0
Future consideration
6
VOTE
Integrate “AHA Idea link” within Feature
My idea is to integrate “AHA Idea link” within feature as soon as AHA idea push to Rally as a Feature We have separate URL for AHA idea therefore to check all critical information like Idea submitter, Business Owner, Comments, Business Justificati...
1
Future consideration
1
VOTE
Ability to select workspace owner/contributor when setting automations
Our use case: We are creating automations where when an initiative is placed in status at risk, we generate an email alert to the owner of the workspace. Currently we need to do this by name specifically, but it would make it more scalable to be a...
0
Future consideration
8
VOTE
Ability to add an epic to a release phase
We use Aha Roadmaps for our roadmap and release planning, with detailed phases that cover development actitivies as well as Go to Market release planning. Currently we run into the problem that since half of our teams use Jira to track their work,...
0
Future consideration
5
VOTE
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
0
Future consideration
1
VOTE
Table templates in dropdown
I often find myself wanting to use different tables for different records. While the record template is nice, when clicking "Add Table" I would love to be able to select template tables and easily drop them in. For example, a "User Story" which on...
0
Future consideration
2
VOTE
New Modern and Simpler UI/UX for Aha
A simpler, more modern UI and UX for Aha would make it easier to adopt across different teams in the organization as a sole-source of truth while at the same time making it easier and more efficient to work with Aha. Some key areas and KPIs includ...
1
Future consideration
4
VOTE
