My team noticed this recently when we moved Visualcron from a server using local time to a server using UTC. As far as we can tell, the Task Result window applies the offset between server and local time twice.
The "execution time"
while a job or task is running also displays as having the offset added to it, which is funny but hasn't really been problematic or confused anyone.
If not for the header/policy (since sometime around the SMA acquisition):
Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.
or maybe if Visualcron's Zendesk were publicly browsable (by default, that is...back when Visualcron handled a lot of support through the forum, I think Zendesk or something similar was still involved for things that needed to be more private), I probably would have reported this already, but...with their Zendesk apparently locked down so that end users have to interact with it via email instead of the web interface, and tickets being private so that other users can't contribute to or benefit from the conversation (at least, unless it results in a fix in a future release), the motivation to go to that much effort for such a minor benefit just wasn't there.