Before you write
Most of what goes wrong has one of these three causes, and each takes a moment to rule out.
No badges appear
Open a Jira issue or board and give it a few seconds; the badges appear after Jira has finished drawing the page. If they still do not, the extension may be looking for part of Jira's page that Atlassian has since moved. Turn on Print what the extension is doing to the browser console in the extension's settings, reload the page, open the browser console with F12, and send what it printed. That output says exactly what it could not find.
The numbers look too large
By default every hour counts, including nights and weekends, so an issue left on a Friday collects the whole weekend. Turn on Count working hours only in settings and set your working week. Sunday to Thursday is supported, as are your own public holidays.
A badge disagrees with the panel below it
The badge counts the current visit to a status. The breakdown counts every visit, which is why an issue that was reopened can read In Progress 1h beside In Progress x2, 4h. Both are right, and the "x2" is the clue.
Reporting something
What makes a report quick to act on:
- What you expected to see, and what you saw instead.
- Whether it was on a board, an issue, or the report page.
- A screenshot, if there is anything visible to point at.
- Console output, if the problem is a missing badge.
Please do not send anything confidential. Screenshots of real issues often carry customer names and internal project detail, and none of that is needed to fix a bug.
What the extension does with your data
Nothing leaves your browser. The privacy policy is short and says exactly what is stored and where.