Documentation

Where Workline appears in Jira Cloud once installed: the Apps page, a Workline tab in each space and a gadget, and the first steps for an admin.

How to read the plan: a row per person, a column per week, the share lozenge, Total, Unscheduled, bookings, and how hours are placed.

Plan in story points where your work items carry them: how a person’s pace is worked out from the last 6 weeks, and the points a week a Jira admin can set.

Add the last 2 or 4 weeks to the plan: the hours each person logged, or the story points they finished, against what they could work.

Name roles in the settings, filter the plan by role, and show a row per role, epic or space instead of a row per person.

Set aside part of a person’s time with no estimate behind it: what for, the days, a share or hours a week, and how it counts with estimated work.

A row for someone you have not hired yet: its name, first day and hours, bookings on an epic or work item, and how to fill it with a person.

Reassign a work item from someone over capacity to someone with room, seeing everyone’s load before and after. What Jira changes and who may.

Press a person’s Unscheduled hours: Workline suggests start and due dates in the days they have room, highest priority first. What Apply writes.

The hours each person can work: Jira’s time tracking or Workline’s own, part-time hours, holidays for everyone and a person’s time off.

Teams are Jira groups a Jira admin offers: a team’s members each get a row, with or without work. How to offer one and how to plan it.

The site-wide settings a Jira admin can change: the working week, own hours, holidays, time off, the groups offered as teams and who can book.

The permissions Workline asks for, what it reads and writes and as whom, what it stores in Forge storage, and why nothing leaves your Atlassian site.