We use Proof quite a lot, and path #1 is the one we take. This reduces
touch points for us, and keeps the feedback direct. Project Managers
only get involved with a proof if things are not staying on track.
I tested his just now in one project, in my production environment In
the New Experience, and it seems to work for me. While viewing the task
page I did not have any Issue getting the task date to change and stick
permanently, and the task constraint updated to Must Finish On as I
would expect. Not ...
I also ran into this issue this week. Support sent the usual
instructions to "click on the logo" to grant access, and since that
doesn't work in NE it took me a minute to sort out how to grant them
access. My suggested implementation for granting access would be to send
a system notification / annou...