Status changes + time tracking automation

I want to count how long the pulse was in progress and I try to do it with automation:
When status changes to in progress, start time tracking. When it changes to anything stop.

But I see that time tracking turns on for a couple of seconds and then turns off…

In this case I understand that I need to use automation: When status changes to in progress, start time tracking.
And for all other statuses (I have 9) add automation: When status changes to something, stop time tracking.

In my opinion it is not very convenient… and it would be cool to have automation like: When status changes to something, start time tracking. When it changes to anything else stop.


Hey @SlaveZ,

Justin here :slight_smile: Thanks for your feedback.

I will be sure to pass this feedback along to our automation team. With that being said, for feedback purposes what happens if you set when status changes to anything start and do the same for the stop. Does this still cause the same stop?

Let me know.


Hi Justin.

Case is the same time tracking start at few second an then stop.

It’s look like we use one automation after another.

I can use two step automation, like on screenshot below…

Now order matters, but I can’t change it. And i didn’t know how it will be work in future

This is awesome. Thanks for sharing!


I edited the message

I second this improvement! I need this feature to see how long a request is stuck in a Waiting for Client Status! Please consider this improvement.

1 Like

Hey @cfraticelli @SlaveZ,

Thank you so much for sharing this. It makes so much sense and I see what is happening. I will be sure to pass along this feedback to our team for review.

What I do believe is happening is that working on it counts as anything for the second automation and stops the time tracker immediately.

What are the chances you can make “stop” automations for all of the different labels that this can be changed to? Although this adds more automations, it should act like the “anything” scenario you want, while preventing it from stopping when selecting working on it.

Will this work for now?

Let me know.


1 Like

I’m having the same issue too, and while we can certainly use your suggestion @JustinJ… it isn’t the most sustainable. Since we may add a new status at some point, then must remember to also update a hard-coded automation… would be best if the anything column worked as it seems to be designed, if possible.