-
Bug
-
Resolution: Won't Fix
-
High
-
23
-
Severity 3 - Minor
Issue Summary
The columns in the List View of JWM are reset to default after the user logs out and closes the browser and are not persistent after user logs back in.
Steps to Reproduce
- Open the list view of JWM project
- Add/Remove Columns as needed
- Logout of the Jira session
- Close the browser
- Open the browser again and login to list view
Expected Results
- Changes made to the columns prior to closing the browser persisted
Actual Results
- The list view shows default columns and the user loses all the changes they made to the columns
Workaround
The List view is storing column configuration in browser local storage which is why they are not persisting when you change browser or log out of Jira. As an alternative, you can use the "Issues" tab in List mode which will persist your preferences - https://support.atlassian.com/jira-software-cloud/docs/search-for-issues-in-a-project/.
- is related to
-
JWMCLOUD-136 View configuration should remain across devices and browsers
- Gathering Interest
[JWMCLOUD-772] The columns in the List View of JWM are reset to default after user logs out and closes the browser
Hello,
How can you call this expected behaviour?! Our teams have been waiting over 1/2 year for this to be fixed, this is unacceptable!
Hi everyone,
This is Aidan from the Jira team. Thank you for bringing this issue to our attention, but this is the current expected behaviour of the list view.
To set the right expectations, we are closing this bug as ‘Won’t Fix' as we do not have any plans to change the behaviour of this feature. As an alternative, you can use the "Issues" tab in List mode which will persist your preferences - https://support.atlassian.com/jira-software-cloud/docs/search-for-issues-in-a-project/.
Thank you again for providing valuable feedback to our team! I will be marking it closed for now.
Aidan
My organization recently changed their policy, so I am logged out now after a certain period of inactivity. For me that equates to logging in to Jira roughly twice a day. So having to continuously recreate the list makes the list view virtually unusable. Please fix ASAP!
This adds a lot of manual steps to continuously have to recreate the list as desired. And every user has to do this every time they log out. We would really appreciate for this to be addressed!
This bug has a negative impact on our internal rollout for using Business Projects within our organization. Following for any updates, workarounds & hoping for a fast resolution. TY!
We are also effected by the same issue.
Is there an update on when this issues is anticipated to be fixed?
We are experiencing the same issue.
The problem is that the individual user's settings (filters, grouping, columns etc.) are not saved on user level. They go back to defaults after the session is restored (time has passed, logged out, private mode, using another device, using another web browser).
In my opinion keeping the settings on user level is a must have functionality - same as on any internet browser (e.g. chrome, edge) - if you login on any device you'll see all your favourites etc. on any pc you use.
This bug was also mentioned in JWMCLOUD-136 (although task got changed from BUG to Suggestion! 
) The bug has not been fixed yet despite Ben's comment from 5 Oct 2023: We've noticed user level persistence has been inconsistent and we're rolling out an update to our persistence model in the coming weeks to fix this.
The number of people affected is actually growing in out teams, however that may be possible...
I agree with Luka, it is unacceptable to not be working on a solution. Jira publicly advertises the list view being customizable: [Customize your list by adding or removing fields | Jira Work Management Cloud | Atlassian Support|https://support.atlassian.com/jira-work-management/docs/customize-your-list-by-adding-or-removing-fields/]. This bug makes that customization unusable. I have not found the "All Work" tab list mode that you reference Aidan as an alternative. Please provide more information so I can assess if it is a feasible alternative for my team. Thank you.