Important Update: Transition from List View to Table View ๐
Pinned FeaturedHi everyone!
We have an important update for you regarding a change happening soon: the transition from List View to Table View.
Why the Transition?
As you may recall, the (New) Table View was designed with the objective of combining the features of both List and Table views, offering a comprehensive way to track and manage your work within Wrike. The move to a singular view aims to deliver a more unified and intuitive user experience, simplifying tasks and enhancing workflow efficiency.
The List View was built on older technologies we can no longer support. Sunsetting this view will help improve product performance and future improvements to the Table view.
Enhancements Based on Your Feedback
We greatly appreciate the feedback youโve shared, and our team has implemented several updates to facilitate this transition:
- Public Links: Easy sharing and collaboration
- Mass-Enabling Project Progress
- Undo Button: Quick recovery from mistakes
- โSelect Allโ in Mass Actions: Simplifies bulk changes
- Wrap Text: Improves readability
- Remembered Collapsed/Expanded State: Customizes your view settings
- Mass Actions: Switch assignees & shift dates easily
- Better visibility into custom fields with rich formatting options
- Grouping by any system or custom field
- Interactive Files column: allows to work with files right from the view: preview, download/upload, proof.
Weโve also made the Table View more user-friendly by supporting a compact, less cluttered display. You can now select between compact or default density, enable or disable any fields represented as columns, and choose between viewing tasks and subtasks hierarchically or in a plain list format.
Additionally, mass editing capabilities for projects and folders - previously unavailable in the old List View - have been added to enhance your workflow.
Transition Timeline
We aim to complete this transition by the end of March 2025, providing you with ample time to adjust to using the Table View exclusively. During this transition period, we encourage you to explore its functionalities and share any feedback you may have.
At the time of the transition, all existing List views will be migrated to Table views that will be configured in the same way as List to show the same information, in the same order, and keeping all the view settings like filters and sorting.
We're Here to Help
Our team is here to assist and address any questions or concerns you might have during this transition. Our Product team is also working on more enhancements aimed at improving your experience with Table view even further.ย
We truly appreciate your understanding and support as we work to enhance the platform for everyone.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Lisa thanks for this update! My team loves the new table view. The only thing we are still using the old list view for is to mass unfollow things. Is there any plan to add this to the new table view or will this ability die with list view?
Lisa Throughout the entire process, this phasing to the new Table view has been billed as essentially maintaining the features of the List view, but I have been raising concerns for the last year about the fact that the new Table view is showing subtasks twice, once in the proper hierarchy as a child task under a parent task, and again at the 'root' level of the table.ย
I've been told repeatedly that this is because the subtasks are 'tagged' (whatever that means, which no one from Wrike actually explains or defines) with the parent project, and that in order for the subtask not to appear twice I need to 'untag' from the project.
Now, 'tags' aren't a thing in the API structure.ย It appears I'm being told that I need to decouple/disassociate the subtask from the project altogether, but that can't be right, surely?ย It seems poor design to have unassociated tasks just floating around outside of any project to which they obviously belong to, and also means that any dashboards in which these subtasks would show, will not have any reference to the project they relate to, it will just be a list of unidentifiable Tasks. which we do not want and will not realistically be able to use.
Can you help me by actually explaining why:
a) the List view is being forcibly retired anyway?ย No articles or communications seem to actually explain this aspect, they all just tout the virtues of the new Table view, despite it's glaring holes
b) why the new Table view does not have any functionality to behave like a table should (i.e. not showing subtasks twice)?ย If Wrike know that this a behaviour, why can we not simply have an option to have it not show hierarchical subtasks at the 'root' level of the table?
c) why the old Table view displays the hierarchy correctly, but the new Table view does not?ย It seems like Wrike has gone out of its way to fundamentally change the behaviour of the new Table view, for reasons I can't quite understand
I'm with Nick. For our organisation we live by the listview. Tableview is good for some applications, but for a simple overview/List you just can't beat the List view.
We've noticied the slow death of the List view where more and more features are going towards the Table. We just experienced that Tableview has an icredibly worse performance for us when loading proper amount of Tasks. Whilst Listview struggles less.ย
It will be very painful for us to see Listview go.
Hi Lisa,ย
Is it possible to retire this view sooner for individual accounts? We dont use this in my company so I would be keen to turn it off sooner than the end of March.
Cheers
Aram
Any word on bringing back the ability to sum effort in Table view? This feature was removed with the old table view, but for anyone who wants to see how effort is tracking, this is pretty essential!
Hi Nick,
it seems you misunderstood the tagging system in Wrike. Subitems needs to live in the same folder as their parent item, so they are automatically tagged into the parent folder. This is called Ghost tag. If you additionally tag a subitem to a parent folder, you'll get the result you described. Removing the tag will not result in a "homeless" item, until it is not detched from it's parent item.
See Ghost Tags โ Wrike Help Center
Hope this helps, Florian
Hi Lisa
I really hope Wrike is going to implement full mass editing functions to the table view before sunsetting list view!
Please, don't mess it up!
Mass Edit โ Wrike Help Center
Mass Unfollow in New Table View โ Wrike Help Center
DO NOT Remove List View โ Wrike Help Center
Keep List View โ Wrike Help Center
I asked in a few other places, but never really got a concrete answer.ย
How will this phasing out of List view impact some areas of Wrike that don't allow for us to swap view, namely in the Recycle Bin and the main Blueprint page? Will they still act in List view or will they be transitioned over to Table view?
Personally, for something like the Recycle Bin, having Table view doesn't seem helpful.ย
Florian Kislich In the subtasks within our Wrike environment, there are no 'ghost tags' visible, so I'm not sure this is the issue.ย Every single Project, Task and subtask in our Wrike environment is created programatically using API calls, and there is no functionality to control tags (which appear to labelled 'Locations' within the UI) using API calls, and with these tags being automatically applied, I appear to have no control over them.ย I 'm guessing the issue arises, not from the ghost tags, but from the tags/Locations themselves.
I understand this functionality, and it makes sense to me, what doesn't make sense is Wrike forcing out List View without providing a functional replacement (i.e. List View - and in actual fact the 'old' Table View' - does not have any issue with displaying subtasks twice).ย I'm at a loss to understand why these ghost tags cannot be removed (either programmatically or via UI).ย The advice (according to the page you linked) is to change a subtask's location, but with only the project as a tag, where else am I supposed to move it to?ย I tried using the detach function, but this only seemed to detach it from the parent task, which is the opposite of what I'm trying to achieve.
Also, without the project tag, when using a dashboard, the list of subtasks (I have filtered out the parent Tasks as they are not necessary to see for us), there is no context for the subtasks, as I believe the parent project that displays for us in the dashboard is in fact the project tag.ย As I'm sure you can appreciate, this is less than ideal for us, and it is all driven by Wrike's insistence that List View be retired, despite the protests of some of it's own customers, and without any explanation as to why.ย I fear this will result in us leaving Wrike for one of their competitors that offers functionality that users actually want/need, without forcing unwanted/unneeded functionality upon it's customers
Florian Kislich UPDATE:ย I believe I have found a possible work-around:ย When playing around I noticed that if I remove the project tag/Location of a subtask using the wee X button on the tag/Location, the ghost tag/Location of the same project was displayed in its place, and the 'duplicate' task removed itself from the root of the Table View.ย When checking the Task via APIs, I noticed that this had the following behaviour:
- Project ID removed from 'parentIDs' array and added to 'superParentIds' array
- 'parentIds' array had a guestRoleId added to the array
I will attempt to see if I can set this when creating new projects/tasks/subtasks via API calls
Florian Kislichย UPDATE 2:ย Ok, the above seems to work.ย I made a slight error/mistype in the above comment, namely that the 'parentIds' array has the root folder added to it, not a guestRoleId (they were very similar strings and my eyes mistook it for a guestRoleId on the Space).ย To achieve this I did the following:
POST https://www.wrike.com/api/v4/folders/{root_folder_ID}/tasks?title={task_title}&superTasks=[{parent_Task_id}] + any other parameters needed.ย By using the {root_folder_ID} we appear to avoid 'tagging' the project directly onto the Task, and the ghost task does it's job.
It's also worth noting that the ghost tags will still display in relation to the Task/subtask in a dashboard, so we do not lose context
I also agree with Florian Gascho that the performance of the list view was so much better than table view. But as the Wrike team told, it is based on old technology they want to get rid of...
Hi Nick,
you said
I'm not sure about the old table view, but I tried to reproduce it with list view. Am I right this only applies when using the "single list of tasks" option?
I still don't see why we can't have a "New List view" updated to a new technology. I've seen countless Wrike Deminars on how great the table view is and credit where its due there are many places I do prefer that view. But usually me and most of my colleagues end up working in Listview as its a more compact and performant way of accessing data and tasks.
When training colleagues I do try to point out the added benefit of the Tableview but for 'regular' users, it is too slow and too overloaded. For Powerusers it can be a fun tool though.
Hi everyone, thanks for letting us know your thoughts, we've been working with lots of feedback on this topic lately - it's very helpful!
We know that there are still gaps like the follow/unfollow option in mass actions - out team is working on this and some other additions as well.ย
Nick Shorter Great to see it's now working for you, but if you have any questions on tags, please let me know - I can raise them to our Support team if you want.
I've also brought up your concerns with performance of Table view Florian Gascho. We may need to investigate this further.ย
Aram Roberts I'll raise this with our Support team - they may be able to do it for you.ย
Kirstie Dyment This should be possible already with calculations in Table view, pleaseย see this article for more info (it mentions there at the bottom that calculations work for the Effort column as well). Let me know if you have any additional info on this.
Florian Kislich Our team is on it ๐
Anna Giacobbe The plan is to move smart folders to Table view as well. Why do you think it won't work for them?ย
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Lisa thanks for forwarding it!
ย
We've overall experienced some performance issues. Eventhough we just migrated the Account to the closer Datacenter, the Performance is still fairly lackluster at times...
Florian Kislich Not 100% sure I completely understand your query.ย I can only see the 'single list of tasks' option under the 'subitems' button in Table View, I cannot see the equivalent within List View at all
Florian Gascho Agree it's a real shame Wrike does not appear to be upgrading List View to work with the 'new technology', I feel there is enough community outreach regarding the phasing out of List View that they should already have considered not retiring List View altogether
Nick Shorter as far as I know this has been a topic even before Lightspeed. So far we've been able to atleast keep the Listview eventhough it continously lost features... Many of the colleagues within my Team hope for that as well! Totally agree with you
ย
Hi Nick Shorter,
coming back to your latest question. The option I was regarding to in List view is called "Tasks from subfolders", which is eqivalent to "Single list of tasks" in Table view.
See List View in Wrike โ Wrike Help Center:
ย
Our company really liked and relied on the list view for efficient planning. The new view makes it difficult to re-organize tasks, add hours, plan peoples time and isn't visually appealing. We would really like the option to use the list view to maximize our PM planning and tracking. Thank you!
Is this change part of the shift to table view? My team is very unhappy with the way this looks. :(
ย
Can you please explain why the list view is being forcibly retired? Me and my teams' Wrike pages have been automatically updated to format in the table view, and it has caused so much frustration - as we all prefer the list view and believe it is much more user friendly. Additionally, when I look at my projects all of my tasks and sub tasks are order correctly, but when I click into a specific task it will reorder the sub tasks. This has been incredibly frustrating as it is not as user-friendly in the table view to rearrange subtasks.ย
I beg you to re-consider retiring list view! Table view has been nothing but a time waster for me and my team!ย
Anna Wallace try hitting the button labelled 'Open default view'.ย I found that this cleaned up the subitems view in the pop-out panel on the RHS
Agreed Anna Wallace it's super messy and our team is very unhappy with it as well. The open default view doesn't work and everything is out of order. Nick Shorter
Some users on our account have been moved to table view in subitems and it's been very disruptive to our work. We were not told that list view would be removed from subitems, it's a very chaotic look. I'm already having to build table view templates for our space and project levels that will need to be applied to thousands of projects but I don't see how to apply a template to the subitem view but even if we could, that's another several thousands of parents tasks I will have to manually switch over. I'm not quite sure why list view couldn't be rebuilt on the new technology like the other views were.ย
Agreed Lauran Janssen it is very chaotic and messy.ย
Lauran Janssen agreed! It's been very disruptive to our work as well!ย