Mar 23 2021 04:19 AM - edited Mar 24 2021 08:07 AM
Hey all,
I've been racking my brain for days on this one and can't figure it out. I've changed the default work hours in my project to 9:30 -> 18:00.
I've done this:
Despite all of this when I drag a task in the gantt or team planner view, when zoomed out to day level or higher, it schedules the task for 8am on the day I drag too.
Does anyone know of any way to change this behaviour?
Mar 23 2021 05:18 AM
Mar 23 2021 05:43 AM
Mar 23 2021 04:38 PM - edited Mar 23 2021 04:40 PM
SolutionDale asked me to take a look at this and here is what I found.
This is an interesting issue. I can drag tasks around all day on the Gantt Chart view and they always pop right onto the correct 9:30 AM start time, but, if I try to drag on the Team Planner view, they always pop to the incorrect 8:00 AM.
Of course dragging tasks around normally results in a start-no-earlier-than constraint and if you look at the Constraint Date in Team Planner view the constraint date always takes on an 8:00 AM time. In the Team Planner view if you drag a task and then double click to open the Task Information and reset the constraint date time to 9:30 AM, it “sticks”. I had a couple instances that once the constraint date time was “corrected” for one task, that setting translated to other tasks, but not always.
Not sure it this helps much but at least it's another input.
John.
Mar 24 2021 03:53 AM
This does help actually - I can confirm your finding that the Gantt view does correctly set the time now - one of the original steps must have fixed that and I've just been assuming I'll get the same behaviour from both.
It's obviously a little inconvenient but dragging tasks shouldn't be a super common operation - I can probably just remember to only do that via Gantt chart for now - whilst the context of the Team Planner is a bit nicer at times, this at least gets the job done without having to go into Task Usage and alter the hours each time (or modifying the constraint time, since you've pointed that out)
Hopefully the underlying bug is addressed some time soon though.
Thanks,
Brizee
Mar 24 2021 08:04 AM
Mar 24 2021 08:06 AM
Mar 24 2021 08:07 AM