Billable hours in Jira, without a billable field
Checked against Atlassian’s documentation on 7 October 2026.
An agency or a consultancy bills clients from the hours its people log in Jira, and not every hour is billable: internal work, support rotas, fixing your own mistakes. Jira worklogs have no billable flag, and Jira has no hourly rates. This page shows how teams mark billable work with Jira’s own tools, where each way stops, then what Logline does.
Marking billable work in Jira
There are three common ways, each on the work item or the worklog:
- A label on the work item, such as
billable, or a separate epic per client. JQL then finds the billable work items:labels = billable AND worklogDate >= 2026-09-01 AND worklogDate <= 2026-09-30. - A field on the work item, such as a select field “Billable” with Yes and No, or a Client field. People pick it when they create the work item, and a JQL search on it works the same way.
- A word in the worklog comment, such as “[billable]”. JQL can
search worklog comments with
worklogComment ~ "billable". It marks each worklog rather than the work item, but only if everyone adds it, every time.
Where they stop:
- Children are not marked. A label on the client’s epic does not reach its stories and sub-tasks, and that is where people log time. So either everyone labels every work item, or an Automation rule copies the label down.
- The hours are all-time. A search finds the right work items, but the Time Spent beside each one is its whole history, from every author, not the month you are invoicing.
- No amounts. Jira has no rates, so hours times rate, per client or per person, is a spreadsheet step every month, after splitting the export’s worklog cells into rows (Export Jira worklogs to Excel).
With Logline
Logline is our app. A Jira admin sets one billable rule and the hourly rates once, in Jira settings › Apps › Logline settings, and every report then shows billable hours and their amount.
Billable time, one rule for the site:
- Everything, except, the rule from install: every worklog is billable,
up to its work item’s original estimate, except in the spaces you pick (your
internal ones) and on work items with a label such as
non-billable, which the stories and sub-tasks under it follow; - Whole spaces: pick a client’s spaces, and every work item in them is billable, with nothing to add on a work item;
- Work items with a label, such as billable, in any letter case;
- Work items with a field value: a select, radio, checkbox or labels field, and the values that mean billable;
- Work items matching JQL, such as
labels = billable OR component = Consulting. Jira checks the query when it is saved, so a typo is refused rather than counting nothing. - Also count work items whose parent or epic matches: label the client’s epic once, and the stories and sub-tasks under it count as billable.
Hourly rates: a default, rates by space, by client, by person and by person in a space, in one currency, each from a date if you like. Each worklog takes the most specific rate in force on its day: its author’s rate in that space, then its client’s, then the space’s, then its author’s, then the default. So a client space carries its contract rate, one person can bill two clients at two rates in the same week, and a new rate leaves past amounts as they were.
What each report then shows:
- On the total’s line, the billable hours and what they come to, beside the hours logged and the period’s dates.
- Billable and Amount columns on every row and on the totals row. With Rows on Space, then Epic, that is hours and amount per client and per piece of work.
- In the Worklogs view, Billable only keeps the billable worklogs, with each one’s rate and amount, ready to go with the invoice.
- Download, then Excel or CSV, carries the Billable (h) and Amount columns.
- Billable hours with no rate (none for its author, client or space, and no default) are counted and named in a note under the report, never priced at zero.
A worked example: the rule is the one from install, the Internal space
is taken out, and the Acme Website space has a rate of 150 an hour. A
developer logs 6h on a story in Acme Website. Nothing is marked, so the
report adds 6h to the billable hours and 900 to Acme’s amount, at the
space’s rate rather than the developer’s own. Had the story sat under an
epic labelled non-billable, its 6h would count in the total and not in
the billable figure, as an hour in Internal does.
Who sees what: everyone who can open a report sees its amounts, and the report prints the billable rule and the rates rule under its total. Only Jira admins see or change the rates themselves; a report receives only the rates of its own spaces, clients and people. Logline reads, it never writes: the rule marks hours in its reports, not on your work items.
Fixed-price work
For a fixed price, the hours past a work item’s original estimate are not billed. Logline does this from install, in every space: a story estimated at 12h with 14h logged shows 12h billable. The hours count in the order they started, so a month you already invoiced does not change when later work runs over. A story’s estimate also covers its sub-tasks that have none of their own, and a work item with no estimate is billed in full.
The work item panel says where the work ends. Its Billable line reads, for example, 456h 30m at 97%, then at end 497h 15m at 76% (the Details column gives the end its own row). A grey line names the hours already past the estimate, and an amber line what will not be billable when the work ends. Reports, amounts, margin, the timesheet PDF, the Xero and QuickBooks files, Excel and CSV count only the billable part.
To bill more on one work item, raise its original estimate in Jira. For a client who pays for overruns, a Jira admin picks the client’s space under Except in these spaces, or turns off Bill up to the original estimate, in Logline settings under Billable time.
Every setting is described in Settings. For the worklog-by-worklog list behind an invoice, see Export Jira worklogs to Excel, and for a client space’s hours month by month, Hours logged in a Jira space per month. More on the Logline home page.
