@Tanya Maddalena Is it possible to do a test run on this feature in my sandbox environment before it is enabled/rolled out to my production site. As it seems there will be many changes, as the admin for my site, I would like a chance to preview and run through it that that I can have information in place and adequately explain to my user base.
@James Woyciesjes It's already live in production though, at least for us. Hope for you it won't, it is not pleasant at all for all of our team since many of the features do not work at all.
@Tanya Maddalena can you please feed back about these issues (especially the inability to Group and still collapse hierarchy). Jira has TOTALLY overcomplicated my weekly prioritisation workflow because I now have no way to hide sub-tasks in my lists when I Group or Filter
@Tanya Maddalena So from my short time messing around with this new "Merged" view it very quickly became obvious you just completely scrapped list view in place of having the All Work view take its place with a few small features from list view that are so poorly implemented that it makes what is already a significant downgrade an even bigger issue.
The issues I have found in the last 15 minutes:
Still no ability to set a default view for the lists to have everyone on the team be on the same page.
Removed the drag and drop formatting ability that List View had which was one of, if not the only, formatting options that had a global effect.
Removed the Ability to have an item open in a minimized view in List View to allow you to quickly scroll and jump between issues while the issue remains on the right side of your screen for visibility.
When opening an Item you are redirected to a new page fullscreening the Item which has one of the ugliest just empty spaces at the top of the item simply to home the new "Return to Search" button in the top right which was incredibly unintuitive to find, and far more unintuitinve that just closing the pop up from list view.
If you try to gain any level of formatting by using the grouping option that was hamfisted over to pretend that List view has any role in this new system completely destroys hierarchies and just spreads the child issues across what groups they are part of rather than under their parent flooding the view unessisarily.
The Sorting by default is locked to Key Highest to Lowest. I have attempted to change this every way I could think but no matter what I do as soon as you go to a different project and return it immediately returns to default.
This furthermore makes me question what the hell the "Freeze Column" option does considering that it is only available on the "Work" Column and seems to do absolutely nothing as it does not retain the sorting whatsoever.
What the hell is the purpose of this change in the first place? We already have the all work view if someone wished to use that. This quite simply removes the functionality and purpose of having Projects be independent pages. As with 2 clicks you can replace that project's list view with a completely different project's Items.
In terms of the "Selling Points" of this change
"Less context switching" - Is completely false, as if you wished to compare issues from different projects together that was possible in the "All Work" tab or from the giant search bar at the top of the screen. However, selecting an issue now opens it in full screen which removes any ability to even see other issues from your list whatsoever.
"More capability" - Also completely false. It has the same capabilities as the "All Work" view already had bar a few minor quality of life features like in line editing. But that comes at the cost of completely losing all functionality, ease of use and formatting capability that was provided with list view.
"Accessible for all" - Again, completely untrue. Many people do not feel comfortable messing around with filters or reformatting a page every time they visit it. Having list view gave the capability of drag and dropping items to create a semi-standardised view for all team members viewing the page. But now it is stuck to your default and returns to that default after any sorting making it a headache every visit.
"Performance-first" - Comparing my private instance on the merged view and my company instance on the normal list view, there is absolutely no noticable difference in load speeds. But there is a hugely noticible difference in performance between being redirected everytime an issue is opened compared to when opening an item in list view into the pop up or side view, both of which are significantly faster and smoother than redirecting to a new page.
It is incredibly hard to believe that you refer to these as "Improvements". Was there any focus group trials? or Early user feedback surveys? Hell, even any internal QA testing for this?
It just feels more and more with each update that is pushed through into Jira makes the user experience significantly worse, while providing little to no benefit in return. This update has just solidified that belief for me.
Please for the love of all admins, give us the ability to set a default formatting for list view. Give us some way where we can provide teams with the view they need to see on entry. Or at the very least give us the regular list view back as while it wasn't great, it was at least usable compared to this.
Great news @Tanya Maddalena ! Are there any considerations in making the new joined "all work" tab more flexible in terms of giving it a standard filter, for instance?
Use case:
using a kanban board to show items from more than one project
when switching to "all work" or "list", not the same filter as for the board is applied, but it defaults back to only the project's items.
While it would be intuitive to have the list view adapt to the board filter settings too, it would help if this could at least be achieved by manually setting a default for the All work Tab - in a project, or better, in a board.
I know, probably there is already a feature request for that...
Atlassian Team members are employees working across the company in a wide variety of roles.
October 13, 2025 edited
Hi everyone 👋🏻
Thanks again for the thoughtful comments, feature suggestions, and feedback. Below are responses to the most common questions that have come up since the announcement of the List + All Work merge.
We’re listening closely and will continue refining the experience based on your input.
đź“… Rollout & Availability
Q: What’s the rollout schedule? We’re rolling out gradually over the next few months. If you don’t see the new List yet, it’s on the way. We’re starting with Free editions, followed by Standard, Premium and Enterprise.
Q: Will the new List be available across all Jira editions? Yes, the unified List view will be available in all Jira plans.
Q: Can I test this in my sandbox before rollout to production? Not formally at this stage. However, you can navigate to the "All work" tab to test out the experience, as this will become the new List view.
🧠Navigation, Filtering & Defaults
Q: Will the new List tab auto-filter to the current project like the old one? Yes, when accessed from within a project, the List will default to only showing items from that project.
Q: Will the All Work tab disappear? What happens to old bookmarks? Yes, once the rollout completes, there will be one unified “List” tab. We are implementing redirects so bookmarks to legacy List or All Work views will continue to work.
Q: Why can’t I remove the List tab? The new List is now one of the primary views of work across Jira. Removing it would break consistency and clarity, the goal is one flexible, powerful list view for all users.
Q: Can I set default sorting or filtering for my team? Not yet, views are currently user-specific. We know shared/team defaults are important and are exploring options for future support.
đź› Features & Functionality
Q: Can I create multiple Lists or saved views? Not currently, but this is a common request and something we’re considering for the roadmap.
Q: Why doesn’t hierarchy work when grouping or filtering? This is a current limitation, hierarchy and grouping/filtering use different data structures. We’re exploring whether we can support both together in future updates.
Q: Can I expand/collapse all issue hierarchies at once? Not yet, this is a known request and we’re reviewing feasibility. Right now, items must be expanded manually. Q: Why can’t I drag-and-drop to reorder when grouping or filtering? Drag-to-rank only works when sorting by “Rank.” Grouping and certain filters override the ranking sort order, which disables drag-and-drop for now.
Q: Can I filter or group by Sprint? Yes, you can. You can also group by additional fields such as Goals, Reporter, Labels, Priority and more.
Q: What does the “Hide done” toggle do? It hides any issue with a status in the “Done” category (statusCategory = Done). You can always customise filters further.
Q: What is the “Freeze Column” option for? It’s designed to keep key columns (like Summary) visible while scrolling. We're improving the behavior and welcome feedback.
Q: Is export supported in the new List view? Yes, the new list view supports exporting in multiple formats. This includes popular formats such as CSV, XLSX and Word.
🔍 JSM & Cross-Project Feedback
Q: Will these changes come to Jira Service Management (JSM) queues? The current rollout is focused on Jira. We’ve shared feedback with the JSM team, but no timeline is confirmed for JSM at this stage.
Q: Why is the experience inconsistent between List and JSM queues? We understand the frustration, the products are built on shared foundations, but evolved separately. We agree this is an opportunity for more consistency and are passing the feedback on.
Q: Can I use JQL across all views and projects? We’ve heard this ask (see JRACLOUD-96198) and are actively reviewing ways to improve query and filter consistency across all views.
🧠General UX Feedback
Q: Why does clicking an item open a full-screen page instead of a side panel? This is a known change from legacy List. We’re evaluating feedback about drawer-based navigation and may revisit this in the future.
Q: Can I set a default filter for List or All Work views (e.g. matching my board filter)? Not currently, but we’ve received several suggestions around saved filters and default configurations, and are actively considering this for future work.
We’ll continue updating this post as more feedback rolls in. Your input is helping shape how we evolve List, and we appreciate the time you’ve taken to share your experience 🙏
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Thank you @Tanya Maddalena - great FAQ list. Always helps with changes ... i would suggest all product owners/managers post things like this on all the posts for all Atlassian changes :)
Q: Why doesn’t hierarchy work when grouping or filtering? This is a current limitation, hierarchy and grouping/filtering use different data structures. We’re exploring whether we can support both together in future updates.
@Tanya Maddalena this is really really really inconvenient and painful with the way our team worked, and is making our work review extremely cumbersome - essentially we need to adapt our workflow to make this less painful.
I cannot understand why you released a product before it is ready.
@Tanya Maddalena No offense, but I don't understand. Half the listed features don't even work.. Hierarchy doesn't work, you can't view parent items linked to a children, you can't group, why remove all the working features of the previous iteration from before? I can understand a rework, but how could this have been approved for production when it's clearly a work in progress that barely functions as it should?
Considering this is already live in production, please give us a feature flag to use the old version until you've finished development on it since it seems very far from ready...
@Tanya Maddalena maybe I am not a sophisticated enough user, but I agree with @David Amyot above - to essentially replace the previous List with the clunky 'all items' List has been a step backwards because Grouping and Filtering does not work with the Hierarchy. As I have mentioned before, please look at Monday.com to see just how flexible and easy Lists could and should be.
36 comments