Visão geral da atividade
Hi Juan, Thanks for the response. Our customer success manager is very aware of our feelings about lightspeed, as we've had several calls. It's unfortunate he doesn't have the ability to exempt u...
Overall, lightspeed just seems like a giant step backwards in terms of product efficiency. There's so many examples of tasks that used to be intuitive and easy, and are now slower and more difficu...
Hi Juan, Thanks for the comment back. So we typically have a task that goes through 3-4 different departments sequentially, each with their own custom fields that updates internal information they...
Ok, I thought maybe I was little quick to dismiss using custom items to fix the custom field problems in lightspeed, so I tested it more this morning - it's still a bad fix at best. A custom item ...
Bubbly is a good description for it - moving important fields off screen and adding the infantile confetti when a task is marked complete is just not a good redesign.
I don't think custom items solves anything, since we're sharing tasks across different spaces and departments regularly. Every department/space wants to be able to see their custom fields easily d...
Yeah, mode switcher really doesn't help much. If I've got 5-10 custom fields that I update regularly, then the rolling section just displays them down the side and off the screen. So I'm now scro...
Yeah, not a good solution. Custom fields used to be compactly displayed at the top of a task. Now they're buried down the side, pas the wrike id and other useless stuff. Custom fields are update...
Yes, if we could delay implementing lightspeed that would be a quite helpful option. Internally we see a lot of negatives in the new lightspeed, and very few improvements.
I agree completely. The new layout for custom fields in lightspeed makes them unusable. I'm not sure what we're going to do once lightspeed is forced on us, as we use custom fields in everything ...
Kudos
| Label | User name | User email | User type | Date | Link |
|---|