Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    5890 Ideas

    JNPowerFactorsContributor ⭐️

    Converted ARR and other currency fields as a default field call for APINew Idea

    I am trying to write some basic calls for collecting reporting data from the Company object using the API and have found that it is not natively possible to collect converted ARR from the API. Support recommended that we create a custom field that holds converted_Arr and or the conversion rate. The problem with this is that it is useful to be able to just call any currency field and sort on normalized data before returning results. Example I want to pull the top 25 companies by ARR in base currency. I want the API to spit out 25 results, not all results, then convert them, then filter again. Also setting up a secondary converted field for every currency field is error prone and an unnecessary waste of database storage and computational resources. And it is prone to error since this would need to be stored individually in every native and custom object.  I would love for it to be natively possible in the api to simply have a call include a .converted field transformation or derived field such as:"select": [    "Gsid",    "Name",    "Arr",    “Arr.converted”,    "CurrentScore.Name"  ] This would ideally convert to the corporate currency defined in the currency management. Alternately it would be helpful to be able to convert to any currency in the currency manager (ie Arr.USD, Arr.SEK, Arr.GBP). This would ideally also function on all APIs with all objects.

    CHillTEContributor ⭐️

    Dashboards: Feature Adoption Widgets: Filter Features by LabelNew Idea

    When adding Features to an Adoption Dashboard Widget, it would be very helpful to be able to filter the Feature list by Labels. There are several features in our product that “live” in one branch of the Product Tree, but have parts that users interact with on other branches, so to keep a true “tree” structure, Gainsght CS suggested that we keep the main feature in its home branch, and the other pieces of it in their respective branches, but apply the same feature “label” to all of them. As an example, our Automations feature “lives” in the Settings branch of the Product Tree - this is where users go to build their Automations. However, users will also interact with Automations in the People and Jobs branches, when confirming whether a triggered Automation should execute, so those “Confirm Automation Execution” features live int he People and Jobs branches. All Automation-related features have the “automations” label applied.Our Product Team wants a Dashboard widget that tracks ALL interactions with the Automations feature, and the only way to get those into a single widget, currently, is to search/browse the very long feature list, but searching is of limited utility because not every feature has the word “automation” in the name. It’s one of the virtues of the Product Tree, that we shouldn’t have to have long/complicated naming conventions for these features, but without that longer naming convention, I won’t be able to easily find those features in the list to add them to that widget.However, if we could filter the list by Label, all of my Automation-related features would show up, and they’d be very easy to select.This is just one of several places I’d love to be able to use feature Labels. 

    jonchenContributor ⭐️

    Configurable email digest for community subscriptionsNew Idea

    Right now, email subscriptions are all-or-nothing per board or per post. There's no way to receive a rolled-up summary of activity across subscribed content on a chosen cadence.For members managing subscriptions across multiple boards, that means choosing between inbox overload (subscribe to everything and get an email per event) or missing relevant posts (subscribe to nothing and check manually). A digest option would give people a middle path: stay aware of what's happening without committing to per-event notifications.The askAdd a digest option in Notification Settings that bundles activity from a member's subscribed boards and posts into a single recurring email.Ideally it would include:Cadence options, at minimum weekly, with daily and monthly as nice-to-haves Scope control: all subscribed content, or a chosen subset of boards Content coverage: new posts, new threads/replies on subscribed posts/followed members, accepted solutions, each linked back to the source An off switch that doesn't require unsubscribing from the underlying boards or posts Suppression of empty digests so members don't get blank emails on quiet weeksWhy it mattersThis is something members and community managers have asked about. This feature will quietly drive passive members stay connected without committing to checking the site, which tends to translate into stronger long-term engagement.