Stopwatch total should be correct in a GET request even when it is actively running

[oscadev]

Right now, you have to stop a stopwatch to get the current time spent on a task using a GET request. Example, you create a task, you start the stopwatch, at the 2 minute mark, you make a GET request at api/boards/id , and you expect stopwatch / total to be "120" seconds, but it is zero. If you stop the stopwatch at 2 minutes, then it will correctly update in the GET request. This is wrong, I think.

A second stopwatch issue I have found is that there seems to be no way to know if a stopwatch is active through the API. I want to build a stopwatch tracker that hooks into Planka, but these two issues make it difficult to do so.

[meltyshev]

Right now, you have to stop a stopwatch to get the current time spent on a task using a GET request. Example, you create a task, you start the stopwatch, at the 2 minute mark, you make a GET request at api/boards/id , and you expect stopwatch / total to be "120" seconds, but it is zero. If you stop the stopwatch at 2 minutes, then it will correctly update in the GET request. This is wrong, I think.

We can't output a clear time via API as it's constantly changing every second. But that's easy to calculate from the response. There are 2 fields:

• startedAt - start time if it's running (otherwise null)
• total - number of seconds the timer already has before startedAt

So, to calculate how many seconds have elapsed since the start - you need to subtract startedAt from the current time. And to calculate how many seconds have passed in total - add total to the previous calculation.

A second stopwatch issue I have found is that there seems to be no way to know if a stopwatch is active through the API. I want to build a stopwatch tracker that hooks into Planka, but these two issues make it difficult to do so.

It can be recognized if the startedAt is not null - then it's started.

[oscadev]

Nice, that works! Thanks