Skip to content
Menu
HelpSettings

Settings

Jira admins change Logline for the whole site under Jira settings › Apps › Logline settings. Only Jira admins can save: the save is refused unless Jira confirms the person has the Administer Jira permission.

What an admin can change

  • Count a worklog on the day it started in: the viewer’s time zone, its author’s, or one time zone for everyone, picked from a list, such as Europe/Riga: every report then shows the same days to everyone who opens it;
  • Weeks start on: the first day of the week;
  • Working-day length (hours), for days in the hours format, and the Working days, for gaps;
  • Hours format: the default for every report, hours and minutes (7h 30m) until you pick decimal hours, days or decimal days; downloads always hold decimal hours;
  • Who may share reports: everyone, or members of chosen Jira groups (Jira admins always may);
  • Who sees whose worklogs (below);
  • Billable time, Billable share colour, Hourly rates, Cost rates and Budgets (below);
  • Fields in Rows: the custom fields people can group the report by, under Fields in Rows and Then by (see Rows and columns). None until you pick them; a report already grouped by a field keeps it listed;
  • Show time by child work item in the work item panel: on by default, each child work item with its hours, estimate and work ratio in the work item panel (see The work item panel). Turn it off where another app’s panel already lists the children;
  • Show recent worklogs in the work item panel: off by default, the last five worklogs on the work item and its child work items, with their comments, in the work item panel (see The work item panel). While it is off, the panel keeps no worklog comment;
  • Add ‘Made with Logline’ under Excel downloads: on by default, one line under the table of every Excel download, linking to lineset.dev/logline (see Export). CSV downloads never carry it.

A report can still use its own time zone rule, week start and hours format. Reset to defaults puts every setting back as it was on install, the billable rule, its colours, the hourly rates, the cost rates and the budgets included.

Billable time

Jira worklogs have no billable flag, so Logline counts a worklog as billable by its work item. Pick one rule:

  • Everything, except: the rule on install. Every worklog is billable up to its work item’s original estimate, except the time in the spaces you pick (an Internal space) and on work items with a label, non-billable unless you change it, in any letter case. Tick Also when the parent or epic has the label and the stories and sub-tasks under an epic labelled non-billable are out too. Leave the label empty to take out spaces only. Teams that do not bill ignore the billable figures, or pick No billable time;
  • Whole spaces: pick the client spaces, and every work item in them is billable, with no label or field on any work item. Use it for spaces that hold one client’s work. A space the site no longer lists keeps its key in the list until you remove it;
  • Work items with a label, such as billable, in any letter case: only what carries the label is billable;
  • No billable time;
  • Work items with a field value: a select, radio, checkbox or labels custom field, and the values that mean billable, such as Yes;
  • Work items matching JQL, such as labels = billable OR component = Consulting. It runs as each person viewing, as one more search per report. Jira checks it on Save: a query naming something that does not exist (a mistyped space key) is not saved, and Jira’s own sentence says why.

A rule that lacks something, such as a label, says what it lacks, with the field outlined in red, once you leave the field or press Save; picking another rule starts it afresh, and nothing is saved until the rule is complete.

A label or field rule can also count work items whose parent or epic matches: a sub-task or story under a billable story or client epic is then billable too, in team-managed and company-managed spaces alike.

Logline settings, Billable time: six choices, No billable time, Everything, except, Whole spaces, Work items with a label (picked), Work items with a field value and Work items matching JQL; the label “billable”, and Also count work items whose parent or epic matches, ticked.
Billable time set to work items with the label “billable”, their sub-tasks and stories included

With a rule, every report shows its billable hours, their share and their amount on the Total row, such as “96h billable 53%” and “$9,600”, and a Billable column after Total on every row, and the rule in words under How this is counted. With No billable time, How this is counted says so: “No billable time: Logline settings set no billable rule.” The Worklogs view says which worklogs are billable, and the exports carry the same columns.

Under any rule but No billable time, Bill up to the original estimate is a switch, on by default. Turn it off to bill every hour, past the estimate or not. While it is on, Except in these spaces takes spaces out, such as a client who pays by the hour; it is empty until you pick one. Its hint: “Hours logged after a work item’s original estimate is used up are not billable. A story’s estimate also covers its sub-tasks that have none. To bill more, raise the estimate in Jira.” What an estimate covers and which hours are cut is in Billable time.

Billable share colour

The billable share in the gadget, the work item panel and the Details column, and the lozenge on a row’s billable hours in the gadget and the child work item table, are coloured by their share of the time logged, as the work ratio is, and the share itself says which band it is in on hover. It is on by default: a share of 75% or more is green, 50% to 74% yellow and under 50% red, on the whole percent the lozenge shows, so 75% is green and 49% is red. The colour is never the only sign: the lozenge always says its percent, and its hover says the band, such as “50% to 74% of the time logged is billable”.

  • Colour the billable share turns the colour off for the whole site. The lozenge is then grey and its percent plain;
  • Green from and Yellow from are the two numbers, whole numbers from 0 to 100 with yellow lower than green. Below yellow is red. Logline says what is wrong with them next to the fields, and the save is refused until it holds;
  • Colours by space gives a space its own two numbers, or No colour for that space, such as an Internal space where no billable time is by design. Add and remove spaces as you do Rates by space. A work item’s billable share uses its own space’s colours, else the site’s. The dashboard gadget spans spaces and uses the site’s.

The colours change nothing Logline reads, so a change shows the next time a panel or gadget is opened. Like the rest of the settings they are kept with Logline’s settings in Atlassian’s storage, and every person who opens a panel or gadget receives them, as they receive the other settings that are not rates.

Hourly rates

The steps are in Set hourly rates.

Rates turn billable hours into an amount. Set a currency (an ISO code such as USD or EUR), a Default rate per hour, and Rates by person, Rates by space, Rates by client and Rates by person in a space, all optional. A billable worklog takes its author’s rate in its space, else its client’s rate, else the space’s rate, else its author’s rate, else the default. A client is a value of the Client field under Budgets, on the work item itself. Every report then shows an Amount column next to Billable and the total amount after the billable hours on the total’s line, whole amounts without their cents. Billable hours with no rate still count as billable; the report says how many hours have no amount, and never prices them at zero. How this is counted names the rates in force or, with a billable rule and no rates, says “No amounts: Logline settings set no hourly rates.”

Everyone who can open a report sees its amounts. Only Jira admins can see or change the rates themselves: a report receives only the rates of its own spaces and people.

Rates from a date

Every rate, the default included, may have a From date. A worklog takes the rate in force on the day it is counted in, the day the report shows it on under the time zone rule: of the rates for one person, space, client or pair, the one with the latest From date on or before that day. A rate with no From date applies from the beginning. A rate whose From date has not come yet is passed over for the next one in the order above.

To raise a rate and leave past amounts as they were, add a new rate with a From date. Changing a rate that has no From date changes every amount, past ones too. Two rates for the same person, space or pair cannot start on the same day.

Cost rates

Cost rates say what an hour costs you, beside the hourly rates it bills at. Set a Default cost per hour and Cost rates by person, Cost rates by space, Cost rates by client and Cost rates by person in a space, all optional, each with an optional From date as the hourly rates have. They follow the same order, and use the currency of the hourly rates. Cost counts every hour worked, billable or not, and the margin is the amount less the cost.

Jira group that sees cost and margin picks one group. Only its members see cost and margin, on screen and in downloads. Jira admins set the rates here and see cost only if they are in the group; with no group picked, nobody sees cost. Everyone else sees amounts only. Logline checks it as the person, before the figures leave Jira, and keeps the answer an hour. The steps are in See cost and margin.

Budgets

A budget is an amount of hours or money on a space, an epic or a client, for the whole work or for each month. Pick the Client field first, the select, radio, checkbox or labels field that names the client on a work item; its values can take a budget or an hourly rate and become a row. Changing or clearing the field removes the client budgets and the rates by client.

Then add a budget: Budget on a space, an epic (its key, such as ACME-12) or a client, In hours or money, the Amount, and For the whole work or each month. A budget for the whole work of a space or a client needs Counting from, the day it counts time from; an epic’s counts all its time. Adding a target again replaces its budget. Logline keeps up to 300 budgets. The steps, and where reports show them, are in Set a budget.

Saved reports

Under the settings, Saved reports lists every saved report on the site, whoever owns it and whoever it is shared with: its owner, who it is shared with and how many editors it has, and when it last changed, ten at a time with Show more. Change owner hands a report to the person you pick: the new owner can change, share and delete it, and the old owner keeps only what its sharing gives them. Delete removes it for its owner and everyone it is shared with, after you confirm. Both apply at once. Only Jira admins see the section, and Logline asks Jira that you are one before it lists or changes anything.

Who sees whose worklogs

By default everyone sees everyone’s worklogs, as far as Jira lets them. An admin can keep that to chosen Jira groups: their members, and Jira admins always, see everyone’s worklogs. Everyone else then either sees only their own worklogs or cannot open Logline.

Someone who sees only their own worklogs gets every report, one shared with them included, the dashboard gadget and the work item panel built from their own worklogs alone, and each says so: “Your Jira admin shows you only your own worklogs in Logline.” Someone who cannot open Logline sees a line saying so in place of every report, the gadget and the panel. Logline checks this itself, as the person, each time it reads worklogs for them, so a page cannot ask for more. Jira’s own permissions still apply on top: nobody sees a worklog Jira hides from them.

When a change applies

Reports use the new settings the next time they are opened. A changed billable rule reads the reports from Jira again; a changed rate, cost rate or budget does not. A changed rule for who sees whose worklogs applies the next time each person opens Logline; a change to someone’s Jira groups shows within an hour, as Logline checks each person’s groups at most once an hour. The same holds for who sees cost and margin.