DO NOT Remove List View
Removing List View from your product makes no sense. Why remove a functionality that works very well? What is the gain by taking away an excellent method for managing projects? The new view is restrictive and cumbersome. That said, go ahead and add it, if you feel you must, but do not remove a valuable interface that works great. Truly, if you are simply changing it for change's sake, it is a mistake. Do not refresh the app for vanity and sacrifice functionality... please!
LEAVE LIST VIEW. DO NOT REMOVE LIST VIEW.
Hi Gregory W Gulley, welcome to the Community! First of all, I'd like to say a big thank you for sharing your feedback with us. Please rest assured that it will be passed on to our team shortly.
While we are planning to sunset List view, we're bringing more functionality to the New Table view, which is really a combination of List and classic Table. For example, it's now possible to mass edit tasks and projects in the New Table (it wasn't possible in the classic Table).
Having said that, we strive to make sure the transition is smooth. Could you please share more details on what you like about the List view so I could provide some recommendations?
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
Ok, apologies for the delayed response. I have tried multiple times to submit a comment, but the page repeatedly freezes up and disallows copying my text before ultimately crashing. I have typed these in another application in order to (hopefully) get them posted.
Problems with New Table view:
Lastly, I am curious as to the rationale for eliminating two perfectly usable views and attempting to meld them into one? It is difficult to imagine a reason that is worth disabling options for users.
Thanks for getting back to me. I hope the feedback makes its way to open ears & minds who can improve on some of these significant feature omissions in the new view. If we have no option but to accept the coming change, it’d be great to be able to continue to do our jobs as efficiently after the change as we were able to prior.
Hi Gregory, I agree qith you in general, but I have to say that it is acually possible to hide any colums, exept index and name, so you should be able to hide the assignee column! The advandage of this colums is that you can use it for sorting and for edititing and copying, so I really like it. But the appearance like in the list view should stay available!
It would be better if we could move the index column. It is of no use to me and simply gets in the way.
Also, I cannot seem to select date ranges using the due date column.
And, it seems the ability to select a group of tasks and change all their statuses at once is no longer present.
Thanks a lot for jumping in Florian Kislich 🤗
Gregory W Gulley Thanks for providing more context! Let me address your points 👇
1. You're right it's not possible to move or hide the Row number column, but it's actually needed for the mass actions you mention in your last comments - you can hover your mouse over them and you'll see a checkbox. If you click on it, you'll see the available mass editing options, including mass editing statuses:
2. The assignee field can be removed using the "Fields" menu:
Also, you can narrow the column to just display the profile image, and the table will remember the state, which means the next time you open it, the width of the column will be as you set it up previously:
3. Same goes with any other columns (= fields) - you can adjust their size.
4. Any fields can be hidden through the "Fields" menu:
I hope this is helpful, but please let me know if you have any additional feedback or questions 🙌
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
Could you explain the intended benefit of the index column, please? It adds clutter, both visually as well as reducing space on smaller screens. This view might be workable, if the index was gone and using it didn't require me to do more work to achieve what I already have - a clean, easy-to-view workspace for organizing projects. Whenever a new project is created using the new view, it is immediately more difficult to see the project components and set dates/assign tasks.
Overall, this view is simply too cluttered. The list view is clean and easy to work with. Why fix something that isn't broken? Please leave a good thing alone. :)
The new view makes project management more difficult. The previous view was clean, simple, and easy to understand. The new view is cluttered and causing frustration when trying to set up new projects and makes it difficult to find what you are looking for when returning to projects. Please leave list view alone!
If I wanted to work in an excel spreadsheet I would...
Hi folks, thank you for your feedback, we appreciate it!
Could you please show examples of when you find the Table view cluttered? I'm asking because you can disable most of the columns if you want to and save the view so that every time you open that space, project, or folder, it will be the same setting. Thanks!
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
I think Gregory Gulley has done a good job of explaining the clutter and there are added steps that need to be taken to adjust our preferences, whereas the list view does not require the extra effort. And not being able to delete the rows in order to accomplish a mass edit option equals an added column that can't be removed. I'd be interested to know what benefits outweigh this change vs. the experience we're having has users. Thanks!
Sheri and Gregory have pretty much said it all. My only add is that the grid lines add to the clutter.
Lisa The issue is, that adjustments have to be made. While it is a nuisance for us project managers to do these adjustments, it becomes an issue for our collaboraters. Our designers, copywriters and editors are easily confused by such fundamental changes and the ease and standardized look of List View is what always helped in supporting them. List view is the same on all Desktop devices, it has no more than the most necessary information and the contents are easily understood visually.
Example: Almost everyone on our team who was introduced to Table View was confused on how to access a project in project view in the new Table View and had issues in understanding the logic behind this.
Getting these type of collaborators started in Table View and maintaing their views will just increase workload for Wrike Admins.
Also, a table layout with visible rows and columns automatically seems to be more cluttered than the ultra clean rows of list view. (Name | Icon | Date with no visual separators, no extra features or other fuss, but with auto width).
This!!! 👆
Strongly Agree with Ralph!
Thanks a lot for the additional detail here, folks! Our team is keeping a close eye on this feedback as they plan more enhancements for the Table view.
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