Hi all, Recently we moved to a SSO setup with Azure Entra ID. However now staff are regularly having to update the columns in their "Queue" views (not List view) because they keep reverting to a default view without key data. Found this ticket that is about the "List" view having a similar issue that will not be fixed.[JWMCLOUD-772] The columns in the List View of JWM are reset to default after user logs out and closes the browser - Create and track feature requests for Atlassian products. We never had this issue until the recent SSO change and were not aware this problem would happen. Is there a known fix to this or one coming? Many thanks in advance.
Phil, your clarification that the columns were configured by admins is important. The next time it happens, I'd check the saved queue configuration before anyone adds the missing columns back.
Open that exact queue's Edit queue screen and compare its Columns list with what the affected agent sees. Then have a second agent open the same queue URL:
• If the saved Columns list has changed too, capture the before/after configuration and time for Atlassian Support. • If the saved list is still correct but the agent's view is different, compare the affected account in another browser and another account in the original browser. That helps isolate account/session behaviour from browser-specific behaviour.
JWMCLOUD-772 documents the JWM List view, so it doesn't establish that this is expected behaviour for JSM queues. I'd keep the SSO timing in the support report as a correlation, without assuming Entra ID is the cause or changing authentication policies to work around it.
Queue configuration reference: https://support.atlassian.com/jira-service-management-cloud/docs/edit-queues/
Hi,
I could not find a public bug for the Queue view that matches this exactly, but two things should help.
1. Put the key columns into the queue itself. A project admin can open the queue, select More actions (•••) > Edit queue and set the Columns there. That column list is part of the queue, so every agent gets it as the default and nobody has to re-add fields after signing in again. Docs: Edit queues (you need to be a project admin).
2. Why it may have started with SSO (my reading, Atlassian has not confirmed this for queues). JWMCLOUD-772, the ticket you found, was closed as Won't Fix because the List view keeps column choices in browser local storage, so they are lost when the user signs out and closes the browser. If personal column changes in queues behave the same way, anything that ends sessions more often will reset them, for example an Entra ID Conditional Access sign-in frequency policy, persistent browser session set to "Never", or a browser policy that clears site data on exit.
A quick test: change the columns, close the tab without signing out and reopen it; then repeat with a sign-out. If only the sign-out case resets, it is the same behaviour as JWMCLOUD-772, and step 1 is the practical fix.
If the columns set by the admin in Edit queue also revert, that is a different problem and worth a ticket with Atlassian Support.
Written with help from an AI assistant.
Thank you for the answer, we will monitor it over the coming weeks and post back with our results including if we lodge a support tickets. FYI - all of our queue filters and columns were setup by admins (all company managed projects).
It looks like you're new here. Sign in or register to get started.