Scrolling glitch when rescheduling projects or tasks
I've noticed a really annoying little glitch when creating a new project from Blueprint. It's actually when you reschedule a project being created or duplicated. If you use your mouse to scroll over the calendar that comes up, it runs really quickly over a number of months or even years, which then makes it necessary to manually go back to the intended year and month, etc. The issue is compounded by the fact that you have to scroll down to even see the calendar, so when you get to the calendar, it starts running the months by. (See image.)
I think that Wrike is aware of this, but it's still there... Any update?
On this one, I have to say that I am disappointed in the answer I've received.
"Have you considered using scroll bar instead?"
Just try going through the process of duplicating a project and see how this works. 99% of users will use their mouse, not the scroll bar, to scroll down to the calendar after making other choices above it. But when you scroll down to SEE the calendar, and the mouse reaches the calendar, the calendar itself begins scrolling very quickly to other months and even years before you realize it. What has happened is that we don't realize that the date shown is not in the current month anymore, so a date gets chosen and saved that may be many months and sometimes years in the future. I don't have to tell you how that affects stuff in Wrike.
Yes... we are trying to make sure to use the scroll bar to avoid this, but frankly, we shouldn't have to. This should be an easy fix.
Thanks Shawn and 👍!
I have the same experience and it should be fixed very soon! It disturbs the workflow a lot.
Anyone else have this issue?? I can't be the only one! As a matter of fact, my whole team has had it happen to them...
@Shawn as I haven't found a related ticket, I'm going to create one for you so that the team could look deeper into it.
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
Nice to see that this issue has been fixed! Thanks, Wrike! 😃