Issue Summary

Currently, JSM Operations Advanced Search feature lacks following functionalities:

First, when we filter the alerts and then save the filtered results using the Save Search button, system registers the saved search using a "big" URL:

In case the filter has to be shared with other people or embed somewhere, it doesn't look good, it would great if system provides simple share-able link for saved searches. Allow a permalink to a saved query (which can also be updated, in one place, when required) so users don't have to update bookmarks etc.

Second, once Advanced search is saved, we cannot edit it, instead we will have to save it in another search, this is inconvenient and system should provide the ability to edit existing saved searches.

Third, currently advanced search does not allow searching using Policies and Notifications data (it does not support any properties around these features). The only way is to use Audit Logs to inspect data related to these operation features. However, we cannot save Audit logs, as compared to saved searches. 

Expected Results

• Advanced search should provide the ability of "share-able" links which can be shared or embedded anywhere instead of using the existing "long" URLs.
• Advanced search should provide the ability of editing existing saved searches.
• Advanced search should provide searching using Policies and Notifications data (it should support properties around these features). It should also allow saving these searches to access at any point.

Actual Results

• Advanced search does not provide the ability of "share-able" links which can be shared or embedded anywhere instead of using the existing "long" URLs. It would be great to allow a permalink to a saved query (which can also be updated, in one place, when required) so users don't have to update bookmarks etc.
• Advanced search does not provide the ability of editing existing saved searches.
• Advanced search does not allow searching using Policies and Notifications data (it does not support any properties around these features). The only way is to use Audit Logs to inspect data related to these operation features. However, we cannot save Audit logs, as compared to saved searches. 

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available