Show more context for added/removed records in retrospective report
I want to understand more about the records that are added to or removed from a release: When was it removed? Where was it moved to? What is its current status? I would like to see this information in the retrospective report
Jeff Tucker
over 1 year ago
in Reports
1
Future consideration
Require completion of certain fields with promoted ideas
Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.
Danielle A
over 3 years ago
in Ideas
4
Future consideration
The "Show In Portal" Column On The "Statuses And Workflows" Screen Should Allow A User To Set ANY Status Value To "Hidden By Default" Just Like You Do For "Shipped"
What is the challenge? Ideas that are in certain statuses, such as "Will Not Do", unnecessarily clutter the portal, are not useful to most portal users most of the time and make it difficult for users to find the ideas they are looking for. What i...
Eric Masur
3 months ago
in Ideas portal
0
Future consideration
What is the challenge? If a KB visitor reviews the documentation and is not able to find the answers they need, we want to provide them two options for getting further help: Submit a Salesforce case directly from the Knowledge Base Open up a chat ...
Allow Idea records to be seen in a now next later roadmap view
What is the challenge? If we want Ideas to be shown in an Now/Next/Later roadmap view, we need to create a custom drop-down and then a custom report. What is the impact? Would allow users to be able to skip having to create a drop-down and possibl...
Anthony Chamy
6 months ago
in Ideas / Roadmaps
2
Future consideration
Trigger automations from an automated delivery risk flag
What is the challenge? When an automated delivery risk is flagged, I want to then enact an automation to trigger notifications and todos to key team members to address the risk. Today, automations only support the manual delivery risk flag. What i...
Max Robbins
6 months ago
in Features
0
Future consideration
Restrict the visibility of specific custom fields to different users
We use Aha! for all our product planning, however we currently do some financial estimates outside of Aha! which we don't want to share with the wider development team. This causes us to fragment our data and use permissions in other portals as th...
Mark Gerrard
about 4 years ago
in Epics
8
Future consideration
What is the challenge? I get a lot of notifications and not all of them are relevant. What is the impact? I can easily miss notifications. Describe your idea We have predefined filters today by workspace and record type. Allow users to create thei...
Who would benefit? Solution managers, business leaders What impact would it make? Enrich OKR brainstorming sessions How should it work? We use an OKR canvas in an Aha! whiteboard to work objectives through to leading and lagging key results. Once ...
Chris Brooks
about 1 year ago
in Whiteboards
0
Future consideration
Allow a list report embedded in a dashboard to show more than 50 records
Currently list reports, regardless of length, truncate at 50 records when embedded into a dashboard. This makes it very difficult to use dashboards to manage large portfolios. There is also no message informing you of the truncation, so we did not...
Guest
over 1 year ago
in Reports
0
Future consideration