Ability to see history in Master Detail custom table
I would like the ability to track the history for updated records captured within a master detail custom table. This ability is much needed to audit who created records, when they were created, and if any other updates occurred.
It is difficult to see the differences in the parent hierarchy in the category tree from the children. It would be nice to see a bit of an indent to distinguish the children from the parent level of an Idea Category. See attachment
Add dependency links to feature card customization
It would be great to be able to have a visual on the feature board of what features contain dependencies and ideally what their dependent items are.
It is currently hard to tell at a glance if features in a release are being blocked etc.
We use Aha! across our product and portfolio management team and are using Aha object and notes to curate exec level reports.
An issue we have is that when creating our own notes (so not from other Aha objects) we don't always get consistent be...
Andrew Fenner
over 6 years ago
in Features
0
Shipped
Well, I’m certainly glad there is a reasonable way to get to these, but in the spirit of constructive feedback, that is a terrible UI… I don’t think most people are going to intuitively think “Oh, let’s look in Roadmaps -> Overview” for my feat...
When I create a new pivot table, and use the big + button to add my own custom pivot report, it always has too much data, takes forever to run, and truncates the data. Why? Because I wasn't able to add any filters to show only my product. By defau...
Jonathon Leeke
almost 9 years ago
in Reports
1
Shipped
All saved views to be shared with individual users rather than product teams
Would it be possible to allow saved views, especially at a report level to be saved with individuals who can see/make changes rather than just product teams. Some times there could be execute views/reports we create that we only want certain membe...
I don't understand why when you move an Initiative from one product to another it loses all associated records. The roll-up and related releases are still relevant & you can link these things across products so why drop them when moving?
When a release is deleted, it should automatically fall off the user story map. Today, the ghost of the release stays on the map and has to be explicitly deleted.