Skip to main content
adam.ballhaussen
Helper ⭐️
May 11, 2021
Released

Support parent/child hierarchy for product areas/features in Ideas and Product Updates

Related products:CC Product Updates
  • May 11, 2021
  • 19 replies
  • 338 views

The hierarchy for Product Updates and for Ideas is flat, as in there is only 1 level.

 

Our organization has multiple “Products” that each have a set of “features”. I would like to see Product Updates and Ideas both support a “tiered” structure for these products & features.

 

Things I’d like to see:

  • Filter Ideas and Product Updates by Product AND Feature
  • Allow customers to select Product AND Feature when submitting an Idea
  • Allow customers to subscribe to a certain product/feature to receive notifications when new updates/ideas are submitted
  • Ability to customize the terms Product and Feature 

 

I imagine the hierarchy would work as follows:

  1. Product A
    1. Feature A
    2. Feature B
    3. Feature C
  2. Product B
    1. Feature A
    2. Feature B
    3. Feature C

Features might be conditional based on the Product that is selected, or if needed for product simplicity the Product could be an unselectable “parent” similar to Parent Categories for Community Categories that only helps organize each feature.

19 replies

Helper ⭐️⭐️⭐️
May 20, 2021
Updated idea status New → Open
Helper ⭐️⭐️⭐️
May 20, 2021

Hello @adam.ballhaussen I really like that idea :). It makes a lot of sense for communities with several products.

I wonder about subscriptions. If an end-user is to subscribe to a product, would you say that they receive notification about all the features?

Also when posting a product update, would you make it mandatory to select a product and or a feature?

adam.ballhaussen
Helper ⭐️
May 20, 2021

Hi @Marion Frecaut. Great questions.

 

Subscriptions: If there were an ability to subscribe to individual products, I would imagine that a user who was subscribed to a product would receive notifications for all of the features. I would be happy with a v1 that still only supports a single level of “subscription” options on the Product Updates page as it is today. Long term though, I could see it being beneficial for users to be able to select more specifically which products/features they are notified about.

 

Posting: I think it could remain optional to select a product and/or feature when posting a Product Update. There are some cases where an update might span across multiple features within a product, so either multi-selecting as a sort of “tag” or simply keeping some updates as “whole product” and some updates as “whole product + feature”

 

For Ideas, I think it should be mandatory to select a product and optional to select a feature

Adam B.
alex.maks
Contributor ⭐️⭐️⭐️
June 6, 2022

Upvoting this after @Anitahg created this idea, and @Cristina linked to this one via this thread:

 

I would like this hierarchy ability in product updates, similar to how things are organized in the community categories or knowledge base. However, I don’t want to lose the ability to tag the product updates in multiple areas - that’s the main reason we use product updates for our articles in favor of the knowledge base.

Content Manager @ C2C, The Google Cloud Customer Community
Cristina
Helper ⭐️⭐️⭐️
June 7, 2022
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
Cristina
Helper ⭐️⭐️⭐️
November 18, 2022
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
Cristina
Helper ⭐️⭐️⭐️
March 13, 2023
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
anirbandutta
Expert ⭐️
April 21, 2023

@Manon, @Sebastian do we know where does this sit on the roadmap? 

It's an opportunity for engagement
anirbandutta
Expert ⭐️
June 8, 2023

the UI for nested Product Areas should also give options to:

  1. multi select so the parent product and certain (or all) feature areas can be selected.
  2. Generate unique urls for the combinations selected for step 1, that can be served as a specific feed anywhere, e.g. on a Custom page Featured link or through a Dynamic widget

 

It's an opportunity for engagement
Manon
Helper ⭐️
June 8, 2023

Thanks @anirbandutta for the extra requirements! Some follow up questions:

  • Generate unique urls: what the url should link to in that case? 
  • How do you see the relationship between Product Areas and categories? Do you want to be able to link a product area to a specific category? 

Thank you!