I would like to raise an issue regarding the Asset Schema view, which has been occurring since last Monday.
Whenever I open my Asset Schema, the filter settings automatically revert to the default columns:
I have to keep changing the filters back to my preferred settings. However, each time I navigate away to review an asset and then return to the high-level view, the filters reset to their default configuration.
This behaviour is becoming increasingly frustrating and is impacting my efficiency. My custom filter settings have worked perfectly throughout the year, and I have not experienced this issue before last Monday.
Could you please investigate why this has started happening and advise whether any recent changes may have affected saved filter preferences?
I would appreciate a resolution as soon as possible.
I can't reproduct this.
If I filter an onbjectand then navigate away to another object or even to another schema and I return to the schema and select the object type, the filter is still active.
Can you try an incognito window or another browser or just clear your cache and cookies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This happens to me as well all over different selections in Assets. Go to an object type and set the columns you want to be visible. Once you exit the object type and come back to it, the columns revert back to the defaults (which aren't great, if we're being honest).
Same goes for searching Assets. Start a search, select the attributes you wish to search by, and find your asset. Start a new search, and the attributes you selected are cleared, and the only options selected by default are Object ID, Key, and Label. So you have to reselect the attributes every time you want to be able to search by something other than those three attributes. It make Assets search absolutely awful.
Same for filters.
I am our Jira admin, and it happens no matter how many different roles I grant myself in Assets. This can be replicated across browsers, incognito sessions, etc., so it is clearly not a matter of browser settings.
It really is a painful interface to use at this point.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just today, one of my users reported this same behavior and said it started recently. I could not reproduce it. My filter stays intact.
Clearly there is an issue with a recent update, but it would be interesting to see what the commonalities are. We ruled out browser and asset role. We also ruled out admin vs. non-admin permissions in JSM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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^].
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The solution to this is to set your Atlassian cookies to Allow (definitely for Functional, possibly for Analytical). Atlassian account | privacy
Once these are set, your filter preferences will be retained from session to session.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.