Danilo Barros

+1 for this feature

In our environment, filtering is needed to allow clientele to self-service to find the information necessary for Release upgrades. In preparation for an upgrade from Release X to Release Y, this would allow clientele to filter out the pertinent articles/information without utilizing internal resources from Change Management, Relationship Management, Product, and/or Release Management. The self-service benefit will allow clients to obtain the information quickly as a best in class service.

For example, if a client is upgrading from Release X to Release Y, filtering would allow the client to easily determine which features or functionality would be included as part of their upgrade across various releases. This would save internal teams roughly 2-3 hours per upgrade. There are approximately 40 upgrades per year. Therefore, the estimated time saved annually is 80 to 120 hours to our internal teams.

Our idea is to ensure that end-users have filter available during their searches, to easily identify the content that they are looking for.

Other valid filtes would also be:

- By creation date (newer to older - older to newer)
- By Last update date (newer to older - older to newer)
- By relevance (We are using tags but as we have multiple articles using similar tags the other 2 filter above would be helpful)