A Jira timesheet CSV works best with one row per entry, and a total row at the bottom. The columns carry the person, the work date, the issue, the hours, the billable flag, and the rate. That structure lets a reader add the rows and check every total above them. This page gives you the template, the column rules, and a worked example with fictional data.
The columns, in order
Use these columns for each entry. They follow the names Daylight's sample report already uses, and its reports help documents the entry-level export: one row per entry, with the client account and one column for each entry field.
- Person and Email. The person who logged the time, not the current assignee.
- Work date. The day the work happened, not the day someone recorded it.
- Project, Issue, and Summary. The issue key ties the row to the Jira work item.
- Account Key and Account Name. The client account that will get billed.
- Hours. Decimal hours such as 7.5, not 7:30.
- Billable and Billable hours. When the flag is yes, Billable hours equal Hours. When it is no, they are zero.
- R&D-eligible. Keep internal project time out of this column.
- Rate and Cost. Cost equals Hours multiplied by Rate.
Jira stores durations in seconds and its log work dialog accepts 7h 30m notation, per Atlassian's logging guide. A CSV needs the decimal form, because spreadsheet formulas do not read 7:30.
How billable flags work
Bill the client account, so client time is billable and internal time is not. In Daylight, time in the internal project is never billable, and the admin marks that project under Time not on an issue. Every other entry can carry a billable flag, and the export keeps the flag.
Which rate applies
Use the most specific rate the configuration allows. Daylight checks four levels in this order, per the reports and approvals help:
- The person's rate on that client account.
- The client account's rate.
- The project's rate.
- The person's default rate.
Costs use the underlying duration, not the two-decimal display value. At 7.5 hours and US$100.00 the row reads 750.00, and the check is exact.
The worked totals
Priya Nair, Mia Chen, and Dan Okafor are fictional people at a fictional agency. Their week of October 19 to 23, 2026 holds nine entries. The week totals 40.0 hours, of which 33.0 are billable.
| Person | Hours | Billable hours | Cost |
|---|---|---|---|
| Priya Nair | 10.0 | 8.0 | US$960.00 |
| Mia Chen | 15.0 | 13.5 | US$1,470.00 |
| Dan Okafor | 15.0 | 11.5 | US$1,430.00 |
| Team | 40.0 | 33.0 | US$3,860.00 |
The two cost checks prove the rate logic. Billable work gives 33.0 hours at US$100.00, which is US$3,300.00. Internal planning gives 7.0 hours at US$80.00, which is US$560.00. The two parts add to US$3,860.00, so the per-entry costs and the person totals agree.
Download the template
Download the timesheet CSV template. It carries the header row, the nine fictional entries, and comment lines that state the column rules. The reconciliation sheet lists the per-person totals and the cost checks beside their expected values. Reconcile your own export in the same order: person hours, billable hours, cost, then the team total.
Where the totals go next
Inspect the sample report to see the same columns filled by a Daylight export, with costs calculated at configured rates. Daylight calculates the totals. It does not create or send an invoice from the export.