Troubleshooting and FAQ
A budget shows less time than Jira. - The first sync may still be running; Settings shows its status. - Only time inside the budget’s period and inside the history window (Settings) counts. - Worklogs restricted to a group or role, and projects blocked for apps in your data security policies, cannot be read by apps. - New worklogs appear within about five minutes.
Some time has no cost. People without their own rate, a role rate or a default rate cost nothing. The Rates tab lists the hours without a rate; add a default rate to cover everyone.
I changed a rate. When do costs update? Within a minute or two. A new rate only applies from its start date; to change past costs, add the rate with an earlier date (or “the start”).
Why can’t some people see the Burnrate page or the Cost panel? They need the “Burnrate: view budgets and reports” or “Burnrate: manage rates and budgets” global permission. See Get started.
Why is there no cost column for people? Costs per person reveal rates, so only people with the manage permission see them. Budget and report totals, and costs by epic, work item and month, are visible with the view permission.
Some names show as “Restricted”. You cannot browse that project or work item in Jira. Its time still counts in the totals.
We use Tempo Timesheets and everyone shows as “Unattributed”. Tempo writes Jira worklogs with its own app account. Connect Tempo in Settings (beta) with an API token from a Tempo admin who can view all worklogs; this needs a Tempo Timesheets subscription. Burnrate then reads every worklog from Tempo and ignores Jira’s copies.
Can I use more than one currency? Not yet. All amounts use the currency set in Settings; changing it does not convert amounts.
Does Burnrate change anything in Jira? No. It only reads worklogs and work items.
Does Burnrate send data anywhere? Without the Tempo connection, no: it runs on Atlassian Forge and makes no calls outside Atlassian. With the Tempo connection on, it reads from Tempo’s API. See the privacy policy.