Time Tracker by Tempo is not counting (stuck at zero)

[John Garnham]

Time Tracker was working fine this morning. I started a tracker after lunch and it was sitting at zero (0h 0m 0s) for 15 minutes before I deleted the tracker and tried again. I have disabled and re-enabled the tracker, restarted Chrome. Logged out and reauthenticated, but it still won't work.

Any suggestions?

[Brant Schroeder]

@John Garnham Welcome to the Atlassian community

• Is this happening in all browsers?  Have you tried any other browsers?
• Do you have any extensions installed in Chrome? 
• Have you cleared Chromes Cache?

I am wondering if it is a cache issue or an issue with an extension in Chrome.

[John Garnham]

@Brant Schroeder thanks for responding.

I believe "Time Tracker for Tempo" is a Chrome only extension, therefore I haven't tried other browsers.

I have one other extension installed in Chrome which I don't remember installing and may have come with Chrome, which is "Google Docs Offline". I suspect it's been there all along, so I'd be surprised if that were it, unless some conflict has just inadvertently arisen.

I have just deactivated "Time Tracker for Tempo" closed and re-opened Chrome, cleared Cache (Time range: All time; Browsing history; Download History; Cookies and other site data; Cached images and files), closed and re-opened Chrome, opened Tempo page (Calendar view, from my saved link) and signed back in (SSO), gone to the Manage Extensions tab and re-enabled "Time Tracker for Tempo", Authenticated with Tempo, reloaded the Tempo page so the Time Tracker appeared on the bottom left corner of the browser window, selected "Start Tracking".

I still have the same result. Time Tracker is stuck on "0h 0m 0s".

[Brant Schroeder]

@John Garnham gotcha, time tracker by Tempo for Chrome requires browser permission to be setup.  Did you do this?

Configuring Browser Permission for the extension

The extension now appears on top of all browser tabs, hence we require the browser permission to Read and change data on all websites in Chrome settings.

In case you don’t want to provide this visibility to the extension, you can configure site visibility in Manage Extension.

1. At the top right of your Chrome browser, right-click on Time Tracker by Tempo icon and select Manage Extension.

2. Under Site access, click the dropdown menu and select On specific sites.

3. Add the following URL(s) in the text box and click Add Site.

   • *://api.tempo.io/*

   • *://app.tempo.io/*

   • *://(your instance).atlassian.net/* (Your tempo instance URL)

[John Garnham]

@Brant Schroeder yes, it's been just like that, with all those configurations since I set it up about 12 months ago, and working perfectly until midday yesterday, when after lunch I did the same as I always do and started a new timer. I have just attempted to start a timer now (at 8:58AM) and it is currently sitting there for the last four minutes like this "0h 0m 0s".

See below a screen capture of my Time Tracker by Tempo setup:

[Brant Schroeder]

@John Garnham is there another computer that you can test this on to make sure it is isolated to that one machine?  I would suggest making sure that the versions of chrome are the same.  

If everything is working on the other computer I would suggest trying to uninstall and reinstall the app with maybe a reboot in-between.  I have had issues with Chrome apps getting corrupt app cache and not working, could be what is happening here.

[John Garnham]

I'll check on Monday whether any of my colleagues are using it, whether they are having the same problem, and/or whether they can install it and see if they have the same issue.

In the meantime, I have uninstalled the extension, restarted the computer, reinstalled and configured the extension, and still have the same result.

[Brant Schroeder]

@John Garnham any update?

[John Garnham]

Hi @Brant Schroeder , thanks for the prompt. I got one of my colleagues to install TTBT and it worked just fine for him. So, I removed and installed it (again), and this time it worked, and has been working since. That would have been Monday or Tuesday last week (22nd or 23rd July).

I can't think of anything else that changed, just the (second) reinstall.

Thanks for your assistance.