Application

the toolips on estimates fields need consistent messaging in all field contexts, with proper messaging/tip content based on the units of the configuration. this needs to be the UX when creating (actual configured units not a hard-coded either/or t...

apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...

It would be helpful to be able to edit phases and milestones view's visible fields similar to what can be done for releases, features, etc. When adding phases and milestone views to presentations the entire record view is added. Many times one nee...

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...

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

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

Hello, We recently started using Aha to help manage our projects. It is important to note however that those are recruitments projects and not software development. It means we had to change the terminology (because “features”, “release”, etc. d...

I would like to use a Current, Next and Future to produce external roadmaps. It would be so nice to use this report but I cannot as it is today.

When a feature is assigned to a PI, creating new requirements should default to the feature’s PI, as SAFe teams typically deliver all stories linked to a feature in the same PI. Without this you need to manually link the requirements which results...

currently when using the many to many custom field linked to a custom table, a user is able to inadvertently add a record to the customer table from the work item. We would like to make the field many to many but only selectable so the user cannot...