Fix ticket timer, to initialise on reload and after tab sleeping

[Flos]

When the tab was reloaded, and the timer was running, the timer was not initialized again.
When the tab was in background and the tab was sleeping, the timer was missing the amount of time the tab was sleeping.

[github-actions]

Hello & Welcome! :)

Thanks for taking the time to help improve ITFlow. We're excited to review your contributions - we'll review this PR as soon as we can!

Whilst you're waiting, please feel free to check out the forum.

Just so you know, all contributions to ITFlow are licensed under the GNU GPL. By contributing you grant us a perpetual & irrevocable license to include your work in ITFlow.

[sonarqubecloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wrongecho]

Hi @Flos

Thanks for the PR.

Just to confirm, what do you have set in Settings > Ticket > Autostart Ticket Timer?

[Flos]

No, it's not set to start automatically.
I started it manually.
The main point here was that I started a Ticket Timer, worked on a topic, went back to the ticket timer, just to see that only 30 Minutes have passed there, while already over 3 Hours passed by.
Chrome send the tab to sleep for power saving.
After resume, it just continued to count, where it went to sleep, not taking into account the real "start" time of the timer.

[wrongecho]

Ahh I see! Sorry, I just wanted to be sure as this has been a bit of a hot topic in the community previously.
I don't ever have a problem with sleeping tabs but I've tested and this looks good to me!

Thank you!