Better default sorting in filters

We are using Greenshift filters together with a Greenshift Query Builder for listing pages.

Our setup is based on taxonomy filtering. The initial Query Builder order is configured as:

* Order by: Title
* Order: ASC

So in the default page state, the listing is intended to be alphabetical.

The issue starts after the filters are used.

What we are seeing is:

1. The page loads initially in the expected alphabetical order.
2. When a taxonomy filter is selected, the results are filtered correctly.
3. But after filtering, or especially after clearing/removing the filter and returning to the default state, the listing no longer keeps the original Title ASC order.
4. Instead, it appears to fall back to the default post order, which looks like publish date / latest added order.

So the main problem is not the filtering itself. The filters work. The problem is that once the filter interaction happens, the original query ordering is no longer preserved.

From a technical perspective, what we are trying to achieve is this:

* Initial state: Title ASC
* Filtered state: still Title ASC within the filtered result set
* Cleared/reset state: return to the original Title ASC order

At the moment, the behavior seems to be:

* Initial state: Title ASC
* Filtered state: order changes
* Cleared/reset state: falls back to date/default order instead of returning to Title ASC

We also tested the Sorting filter before, but since it overrides the default sorting logic, we removed it from this test scenario in order to isolate the behavior. So this issue can also be reproduced without actively using the Sorting filter, with normal taxonomy filters connected to the Query Builder.

We also tried forcing the query order on our side, but from what we observe, once the AJAX filter request runs, the resulting order still does not consistently stay on the original alphabetical logic. It looks like the filter request may be rebuilding the query with its own default ordering instead of preserving the original Query Builder order.

In short, for the dev team, the key point is:

The Query Builder is configured with Title ASC, but after filter interaction, the filtered/reset query does not seem to inherit or preserve that original ordering.

Thank you again for the support.