So filters on the enrich-ui need an easier way of being saved.
Here is an example query:
{
"resolutions": ["Unresolved"],
"docs": [
{"owner": "Patrick Star"}
]
}
This gets base64 encoded and sent to the GET /tests endpoint to get a filtered set of tests.
In the UI, this process is performed in the filter modal:
As a UX improvement, it would be nice to have the filter that is applied to the test table to be dictated by a query URL parameter that is any base64 encoded query. This way, when a new filter gets applied to the test table, the URL will reflect the query.
This will make it easier to share, save, and modify test queries.
So filters on the enrich-ui need an easier way of being saved.
Here is an example query:
This gets base64 encoded and sent to the
GET /testsendpoint to get a filtered set of tests.In the UI, this process is performed in the filter modal:
As a UX improvement, it would be nice to have the filter that is applied to the test table to be dictated by a
queryURL parameter that is any base64 encoded query. This way, when a new filter gets applied to the test table, the URL will reflect the query.This will make it easier to share, save, and modify test queries.