Idea ID: 2856633

Hot Topic Analytics Requests should not be filtered to requests without offerings

Status : Waiting for Votes
Waiting for Votes
See status update history
5 months ago

Hello,

 

Today the hot topic analytics for requests only work for requests that do not have a offering.

This is very helpfull for customers that are trying to build the catalog, but as soon as they do, it looses value.

I would like to request that this hot topic analytics work for every request depending on having offering or not.

 

Thanks in advance

Jaime Abreu

Tags:

Labels:

SMAX
  • Regarding this idea, here is the business case explaining the idea goal.

    So, today when you use the Hot-topic analytics for requests, it will show the map with the words used in request records that do not have a offering attached. This case, this is very useful if the customer wants to build his catalog from scratch, as will show the main topics used on the request records content.

    From the moment the customers have set their catalog offerings, and the end-users use this catalog, this functionality becomes useless.

    Now, the goal of the idea is to remove the filter to only show request records without offerings, but show all the request records content topics.

    Removing this filter will allow the customer to analyze the catalog offerings vs request contents in a way that they can re-structure the catalog that already have, and expand the catalog to other business areas where the IT is not so knowledge.

    One example that this customer I’m working have. As they are expanding to several other businesses, they will provide the catalog right from the start, but then they need to analyze;

    • The nomenclature of the offerings vs request
    • The most used topics used, so they can put restructure the offering category’s
    • The effectiveness of the catalog that they are offering by analyzing the topic zones

    Regards

    Jaime Abreu

     
  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.