Background

Reports within Assets allows filtering based on object types, object type attributes and attribute values. The current method of storing the filter relies on the filter information being added as URL parameters, for example creating the following URL when filtering on the following data points:

URL:

https://acme.atlassian.net/jira/servicedesk/assets/reports/reports_for_assets_objects_by_attribute?OBJECT_SCHEMA=ari%3Acloud%3Acmdb%3A%3Aschema%2Ffcbfac81-ed9a-4d8e-a7e0-86b3a6be0249%2F11&OBJECT_TYPE=ari%3Acloud%3Acmdb%3A%3Atype%2Ffcbfac81-ed9a-4d8e-a7e0-86b3a6be0249%2F54&OBJECT_TYPE_ATTRIBUTE=ari%3Acloud%3Acmdb%3A%3Aattribute%2Ffcbfac81-ed9a-4d8e-a7e0-86b3a6be0249%2F548&ATTRIBUTE_VALUE=AP-360

Issue

The problem with this methodology is that when a large number of filter options are selected, the URL length exceeds character limitations for the referer header. This causes errors when trying to save  or update filters.

Feature request ANALYTICS-278 - Improve handling of URL length when creating filters aims to improve the error message and prevent adding filters that exceed the current limitation.

Aim of this request

While the feature request shared above aims to improve how the product behaves when the number of filters in use would exceed the current limitation, this feature request raises an improvement on how the filters are stored in the first place to prevent limiting the product in this way.

Ideally the filter options should not be stored as URL parameters allowing for greater flexibility on filtering Assets data.