Ah! I just opened a similar thread and this other issue is referenced in it
So it seems this issue has been around since v3.3.3 and has not been solved 
as it could not be fully reproduced? well that kinda sucks.
Hristiyan Dodov says adding time: true to the field eliminates this problem, may be a good workaround depending on the case.
@tojai Additionally as explained in the issue you linked setting the timezone in index.php to match the timezone of the machine used to access the panel also fixes this. If all users belong to the same timezone that would be enough to fix this for them.