Application

What is the challenge? When viewing the workspace settings, if the setting is inherited from a parent line the user cannot see whether it is enabled, disabled, etc. What is the impact? The user has to drill up into the parent line as many times as...

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

We have implemented two separate scorecards for feature cost and feature impact. This gives us more flexibility in reporting/filtering based on what-ifs. We would like to combine those two scores in an an overall feature score to use for prioritiz...

Who would benefit? Product Owners/Managers What impact would it make? Easily be able to access linked record information from within the parent record such as engineering phase and engineering target date (custom fields.) How should it work? Enabl...

In pivot reports, Aha! offers the options to "Within cells list as:" counts, sum, avg etc. It would be very beneficial if we could filter on this numerical options, especially on counts and unique counts (since it's not a standard option offered w...

When creating reports with custom fields, there can be many fields within an account that have similar names that will display as field options. We use the internal name to help differentiate and allow the user to select the right field they are l...

What is the challenge? The challenge is, we have many products and many releases. We track internal and external release dates but spend a lot of time chasing up PMs to either change their release status or release dates if the dates have slipped ...

What is the challenge? In order to drive more engagement and keep people up to date with feature requests that they are or should be interested in it's often required to add them as followers, if you mention someone in a comment it would make sens...

The circular diagrams in the strategy section(Vision & Diagram) do not visualize well on today's browsers and monitors. Text is too small, data overflows. A more simple Left to right hierarchy would be more understandable, sharable and viewable.

Who would benefit? Users who require all members of an approval group to grant an approval What impact would it make? Right now it only allows "any" member which allows approvals in this scenario to proceed prematurely How should it work? Much lik...