Datum

Docs → Linger Lite

Documentation · Jirav1.4.1

Linger Lite docs

Linger Lite is the always-free edition of Linger. It shows how long each Jira issue sat in each status, in working hours on your site calendar, with every transition listed. It adds the Linger Lite — Time in Status panel on the issue view, a Linger Lite Reports page in the Apps menu and a Linger Lite — Flow Report dashboard gadget.

Getting started

Before you install

  • Jira Cloud. Linger Lite is a Forge app (Runs on Atlassian); there is no Data Center version.
  • A Jira admin to install the app and to set the site's working calendar, SLA target, status groups and field mapping.
  • Nothing to buy: Linger Lite has no licence, no trial and no paid tier.

Install and first use

  1. Install Linger LiteInstall Linger Lite from the Atlassian Marketplace. Everything in it is free.
  2. Set the working calendarOpen Apps → Linger Lite Reports and, as a Jira admin, click Edit calendar. Choose the timezone, Day starts, Day ends, the Working days and any holidays, then Save calendar. Until you do, times are counted Mon–Fri, 09:00–17:00 UTC.
  3. Check one issueOpen any issue and the Linger Lite — Time in Status panel. It lists each status with working time and clock time, how often the issue came back to a status, a traffic light for the current status against the target, and time with each assignee. Click Show every transition to see when the issue entered and left each status.
  4. Run a flow reportOn Linger Lite Reports, report on one project or any JQL and click Run report. You get the bottleneck, cycle and lead time with P50/P85/P90 and each status coloured against your target, over the 1,000 most recently updated matching issues.
  5. Add the dashboard gadgetOn a Jira dashboard, choose Add gadget, add Linger Lite — Flow Report, pick a project and save. It shows the bottleneck, cycle and lead time (P85) and work past its target.
  6. Ask RovoIf your site has Rovo, open the Linger Lite Time in Status agent or ask Rovo chat How long has PROJ-1 been in each status? It answers with working time per status for one issue, P50/P85/P90 per status for any JQL (up to 1,000 issues) and the issues past their target. Answers only include issues you can see.

Configuration

Working calendar

One calendar for the whole site, set by a Jira admin with Edit calendar on the Reports page. It applies to the issue panel, every report and the gadget. Clock time is shown beside working time so you can compare.

One project can also have its own calendar, for a team in another timezone or with other hours: under Project calendars, pick the project in Add a calendar for and click Set calendar. Its issues are measured on that calendar; every other project uses the site calendar.

SLA target and status groups

A Jira admin sets the default SLA target (in working days) and status groups, which combine statuses so you can report on them together, for example Waiting = Blocked + In Review.

Copy time in status into a number field

Create a Number custom field in Jira (for example Days in review) and add it to your projects' screens. Then, on the Reports page, a Jira admin clicks Edit field mappings, picks the field, the status or status group to measure, and working days or hours. Linger Lite updates the field each time an issue changes status; Rebuild fields now fills it for existing issues matching a JQL.

How Linger Lite differs from Linger

Linger Lite is exactly Linger's free plan as its own app. Linger's Standard plan adds reports on up to 50,000 issues, time in status per sprint, working calendars for up to 50 projects, per-status targets, stuck-work flags and alerts, up to 100 synced number fields and 100 saved reports. See Linger docs.

Both apps can be installed on the same site. They use their own panels, pages, gadgets and storage, so nothing clashes; settings are not shared between them.

Charts and insights

On the Reports page (Statuses tab): average or P85 working time per status and a stacked bar of time per status for the 10 slowest issues. The issue panel shows a small bar of time per status.

Language

Available in English, German, French and Spanish. The app follows each person's Jira language setting; Rovo answers, exports and comments the app posts stay in English.

Plan

Linger Lite is free: no licence, no trial and no paid tier. What it includes is read from the same pricing file the app uses. For more, see Linger.

Free

Free

  • Issue panel in working hours on your calendar, with every transition shown
  • SLA traffic light on each issue
  • Flow reports on any JQL or one project (the 1,000 most recently updated issues): P50/P85/P90, bottleneck, SLA colours
  • Time per assignee on each issue + status-by-assignee report
  • Status groups (e.g. Waiting = Blocked + In Review), group by field, P95, rework counts, 5 saved reports
  • Dashboard gadget + CSV download (summary, per issue, per assignee)
  • 2 working calendars: the site calendar + 1 project with its own (timezone, hours, work days, holidays)
  • Copy time in a status or status group into 1 number custom field (JQL, sorting, Automation)

Limits

  • Flow reports and the gadget cover the 1,000 most recently updated matching issues.
  • Saved reports: 5.
  • Field sync: 1 mapping, into a number custom field.
  • Two working calendars: the site calendar plus one project calendar.
  • No time per sprint, per-status targets or stuck-work flags; those are in Linger Standard.

Data & privacy

What Linger Lite stores

  • Time in status is worked out from each issue's Jira changelog when you open the panel or run a report. The changelog is read, not copied.
  • Forge hosted storage, per Jira site: the working calendars (site, plus one project's key and hours), the SLA target and status groups, saved report setups (names and scopes), the field-sync mapping (field id, status or group name, unit), counts from the last field rebuild and cached aggregate gadget figures (no assignee data).
  • In the number custom field an admin maps: the working time in the chosen status.
  • Assignee names are read from Jira to show time per assignee in your browser; Linger Lite does not store them.
  • The app declares no external egress: all data stays in Atlassian.

Linger Lite runs on Atlassian Forge. Data it stores sits in Forge hosted storage for your site, which Atlassian pins to your product's region. See Trust & security, the Privacy Policy and the DPA.

Permissions (scopes)

ScopeWhy Linger Lite needs it
read:jira-workRead issues, their changelogs, statuses and projects to calculate time in status.
write:jira-workOnly to write the one number field an admin maps in field sync (off until a mapping is added). Linger Lite never edits other fields, sets issue properties, comments, transitions or creates issues.
storage:appKeep the calendar, settings, saved reports and the field mapping in Forge hosted storage.

FAQ & troubleshooting

Is Linger Lite really free?

Yes. It is a free app on the Marketplace with no licence, no trial and no paid tier. If you later need more, Linger has a Standard plan.

Why does my report stop at 1,000 issues?

Linger Lite reports cover the 1,000 most recently updated issues that match. Narrow the JQL or project to report on a smaller set, or use Linger Standard for reports up to 50,000 issues.

Can I move from Linger Lite to Linger?

Yes. Install Linger next to Linger Lite. Times are calculated from Jira's own history, so Linger shows the same past data straight away. Set the calendar and targets again in Linger (settings are not shared), then uninstall Linger Lite when you are ready.

How do I uninstall it?

A Jira admin goes to Settings → Apps → Manage apps, finds Linger Lite and clicks Uninstall. Its stored settings are deleted after uninstall. Values already written into a synced number field stay in that field.

Does any data leave Atlassian?

No. Linger Lite runs on Atlassian Forge and declares no external egress.

Changelog

Every release and what changed: Linger Lite changelog.

Getting help

Email support@datadir.co with your site URL and what you saw. Our target is a first response within 1 business day. See Support for what to include, and Status for known issues.