Jira Asset Schema filters reverting back

Hi we have done that and it still the same 

Hi @Michelle Kirk 

Then this could be related to your instance.

Suggest to raise an issue with Atlassian Support, on the topic, as this seems not to be a global problem.

Atlassian's Support AI suggested the following. Item 2. seems most likely:

### 1. Verify Schema Roles
Users must have specific permissions within each schema to ensure their UI preferences (like filters and column selections) are saved to their profile. If a user has only "Object Viewer" access, their settings may not persist across navigation .
* Navigate to **Assets** > **[Your Schema]** > **Schema configuration**.
* In the **Roles** tab, ensure the affected users are assigned at least the **User**, **Developer**, or **Manager** role .

### 2. Reset Cookie Consent
If a user previously selected "Only Necessary" on the Atlassian cookie banner, their *Functional Cookies*—which store UI states—are disabled .
* Ask the affected users to clear their browser cache and cookies for `[*.]atlassian.net` to force the cookie banner to reappear .
* When the banner appears, they must select **Preferences** and ensure **Functional Cookies** are toggled **On** .

### 3. Check for Text Area Sorting
If the filter resets specifically when users try to sort a list, check if they are sorting by a **Text area** attribute. Assets does not support sorting on these fields, and attempting to do so can trigger a UI reset or error .
* **Workaround:** Create a standard **Text** attribute (limited to 255 characters) for any data that requires sorting or filtering .

### 4. Persistent Navigation via AQL
For users who continue to experience resets, using **Advanced Search (AQL)** is the most reliable method. Unlike the basic filter tree, an AQL search generates a unique URL that can be bookmarked. This URL contains the filter parameters, ensuring the view remains consistent every time it is accessed [^03^].