Extend the 'Lock fields based on Status of the record' to Custom Tables
We use Custom Tables in many workspaces to track dollar savings.Once a project reaches a certain status these committed savings should be locked. It would be a great enhancement to be able to do this with Aha!'s 'Lock based on Status' functionality.
Karla Johnson
over 3 years ago
in Reports
0
Future consideration
Better presentation of text when integrating to an existing field in ADO
Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
Aha! Develop: organize the program increment backlog into teams with a filter
The ideal workflow for a SAFe team is as follows: Define work (workspaces and teams): product and engineering define the work to be done Prioritize work (backlog management): work is groomed and assigned to the prioritized backlog Plan PIs (progra...
Dale Potter
almost 2 years ago
in
0
Future consideration
I use the List Report screen to manage my entire pipeline of ideas where I can sort and filter to determine priority. Most importantly, I use this List view to consolidate Ideas by Customer to go over in meetings. While in this view, if a stakehol...
Guest
almost 2 years ago
in Ideas
0
Future consideration
Option to select Features from Roadmap in Features prioritization
When prioritizing features, it would be nice to work on features that belong to one release. So being able to only select the features from a roadmap would be nice
Guest
almost 2 years ago
in Features
0
Future consideration
I'd like to be able to map out a use case map using Whiteboards, and it would be helpful to include a "person" shape. It would also be good to have a "team" shape available
Madeleine Black
almost 2 years ago
in Whiteboards
0
Future consideration
Add the possibility to link individual Component a Strategy Model. The Component can be referenced from various parts of the platform, e.g. Description field of Releases, Goals, Features etc.
Guest
over 3 years ago
in Strategy
1
Future consideration
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
Daniel Pokrývka
over 5 years ago
in Jira
2
Future consideration
Not being able to easily go backwards and forwards in the exam for the certification program is frustrating. Being able to re-review my work would have been better.
Guest
almost 2 years ago
in Training
0
Future consideration