Timesheets, approvals and invoices
These features are part of Burnrate Advanced. They use the same worklogs, rates and permissions as the rest of Burnrate.
Timesheets
Everyone on the site can open Burnrate > Timesheet, even without a Burnrate permission. It shows one week at a time, with a row per work item and a cell per day.
- Each cell is your Jira worklog on that work item and day. Typing hours creates or changes the worklog for you; clearing a cell deletes it. Jira’s own rules apply, so you need permission to log work on the work item.
- Type hours as
1.5,1,5,1:30,1h 30mor90m. Hours are rounded to the minute, as Jira stores them. - Days follow your Jira timezone (your Jira profile setting).
- Cells with several worklogs show their count, for
example
4 (2), and are changed in the work item itself. - Add work items with the search box, or copy the rows of the previous period.
- Worklogs you log elsewhere in Jira show up in the grid within a few minutes.
When the period is done, choose Submit. You can withdraw a submitted timesheet until it is approved. A timesheet that is sent back shows the approver’s note and can be changed and submitted again.
An admin chooses weekly or monthly timesheets in Jira settings > Apps > Burnrate. The choice locks once the first timesheet is submitted. Monthly timesheets are still shown one week at a time, and the whole month is submitted at once.
Approvals
The Approvals tab is shown to approvers:
- People with the “Burnrate: approve timesheets” global permission (Jira admins by default) can approve anyone.
- A person can also get an assigned approver. Managers set this on the Approvals tab. Assigned approvers don’t need a Burnrate permission, and they only see the people assigned to them.
- Nobody approves their own timesheet.
Approvers see the period’s hours per work item and day, then Approve or Send back with a note. Work items an approver can’t browse in Jira are shown as “Restricted work item”, with their hours.
Changes after approval
Jira has no way to stop people changing worklogs, so Burnrate takes a snapshot of the approved worklogs instead. If a worklog in an approved period is added, changed, moved or deleted in Jira later, the period appears under Changed after approval. The approver then chooses Approve again to accept the current time, or Reopen to send it back. Burnrate checks recent periods every few minutes.
Inside Burnrate, an approved timesheet is locked. Time that is on an issued invoice can’t be changed from the timesheet, and its period can’t be reopened until the invoice is voided.
Customers and invoices
People with the “Burnrate: manage rates and budgets” permission see the Invoices tab.
- Add a customer with a name, the address and details to print, and the projects or epics whose time is billed to them.
- Preview an invoice: choose the customer, the period and the lines, one per person and rate or one per work item. By default, only approved time is included; tick “Include time that is not approved yet” to add the rest. The preview shows any time left out because it is unapproved, has no billing rate, or is on a non-billable work item.
- Issue the invoice. It gets the next number in the sequence, with the prefix set in Settings, for example INV-0042. Its worklogs are claimed, so the same time can never be invoiced twice.
- Download the PDF or CSV. The PDF uses your company details and payment terms from Settings, as they were when the invoice was issued.
- Void an invoice to release its time. The number is kept and is not reused.
Amounts use the billing rates on the Rates tab and the billable hours of each worklog. Each line’s amount is its hours times its rate.
Burnrate doesn’t send invoices or connect to accounting software. Use the PDF or CSV with your own tools.
Standard and Advanced
| Standard | Advanced | |
|---|---|---|
| Rate card, budgets, forecasts, reports, Cost panel | ✓ | ✓ |
| Tempo Timesheets connection (beta) | ✓ | ✓ |
| Timesheets, approvals, customers and invoices | ✓ |
Timesheets, approvals and invoices are off while the Tempo connection is on, because Tempo then owns the worklogs.