Docs → Linger
Linger docs
Linger shows how long each Jira issue sat in each status, counted in working hours on your team's calendar, with every transition listed. It adds the Linger — Time in Status panel on the issue view, a Linger Reports page in the Apps menu and a Linger — Flow Report dashboard gadget.
Getting started
Before you install
- Jira Cloud. Linger 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 targets, status groups and stuck-work flags.
- Time in status per sprint needs Jira Software's sprint field and the Standard plan.
Install and first use
- Install LingerInstall Linger from the Atlassian Marketplace. The issue panel, reports page and gadget are free; Standard features need a Standard licence or the free trial.
- Set the working calendarOpen Apps → Linger Reports and, as a Jira admin, click Edit calendar. Choose the timezone, Day starts, Day ends, the Working days and any holidays (YYYY-MM-DD, comma-separated), then Save calendar. Until you do, times are counted on the default calendar: Mon–Fri, 09:00–17:00 UTC.
- Check one issueOpen any issue and the Linger — Time in Status panel. It lists each status with working time and clock time, how many times the issue came back to a status (×2, ×3), a traffic light for the current status against its target, and Time with each assignee. Click Show every transition to see when the issue entered and left each status.
- Run a flow reportOn Linger Reports, set Report on to One project, pick a project and click Run report. You get the bottleneck, cycle and lead time with percentiles, each status coloured against your target, and work that is near or over target. Tabs show Statuses, Status groups, Group by field, By assignee and By sprint.
- Add the dashboard gadgetOn a Jira dashboard, choose Add gadget, add Linger — Flow Report, pick a Project and save. It shows the bottleneck, cycle and lead time (P85) and work past its target for that project.
- Ask RovoIf your site has Rovo, open the Linger 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, and the issues past their target, oldest first. Answers only include issues you can see. Free reports are capped at 1,000 issues; Standard reads up to 5,000 in chat.
Configuration
Working calendar
One calendar per site, set by a Jira admin on Linger Reports with Edit calendar. It applies to the issue panel, every report and the gadget. Working time counts only the hours inside your working days, in your timezone, skipping holidays. Clock time is shown beside it so you can compare.
A project can 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 then measured on that calendar everywhere; every other project uses the site calendar. Free gives one project its own calendar (two calendars with the site's); Standard gives up to 50 projects their own.
- Timezone, day start and day end in whole hours, working days, and up to 200 holidays.
- A working day is the number of hours between Day starts and Day ends; day counts in targets use that length.
SLA targets and status groups
On Linger Reports, a Jira admin clicks Edit groups, SLA & flags. The Default SLA target is in working days for time in any status (3 working days until you change it). The traffic light turns from within to near target at 75% of the target.
Status groups combine statuses so you can report on them together, one per line, for example Waiting: Blocked, In Review = 2. Groups are free; the target after = needs Standard.
On Standard you can also set Targets for specific statuses, for example In Review=1, QA=2 (up to 50).
Reports on any JQL
Set Report on to JQL — any projects, filters to run a report on any JQL (free up to 1,000 issues, Standard up to 50,000), across several projects, with an optional Date range on created, updated or resolved. Linger fetches issues page by page; click Stop to end a long run early.
Reports run as you, so Jira's own browse permissions decide which issues are included.
Saved reports
Save a report setup by name from Saved reports on the Reports page. Saved reports are shared across the site and hold only the name and scope. Saving a JQL or date-range report needs Standard.
Stuck-work flags and stuck alerts (Standard)
In Edit groups, SLA & flags, tick Flag stuck work inside Jira (Standard) and enter Which issues to watch (JQL). Every hour Linger marks open issues in that scope that are past their target with the linger-stuck issue property, and clears it when they are no longer stuck. Search them in any filter, board or Automation rule with lingerStuck = "yes", lingerDaysInStatus >= 5 or lingerStuckStatus = "In Review".
Admins can click Check for stuck work now instead of waiting for the hourly run.
Stuck alerts are off by default. When on, Linger posts one Jira comment that @mentions the assignee, the watchers, or both, when an issue is newly flagged, so Jira sends its usual notifications. Issues already stuck when you turn alerts on get no comment.
Copy time in status into a number field
First create a Number custom field in Jira (for example Days in review) and add it to your projects' screens. Then, on Linger Reports, a Jira admin clicks Edit field mappings, picks the field, the status or status group to measure, and Working days or Working hours, and saves.
Linger writes the total working time the issue has spent in that status (every visit added up, on the issue's calendar) each time the issue changes status. Use the field in JQL, sorting, filters and Automation, for example "Days in review" > 3. An issue that never entered the status keeps the field empty.
To fill the field for existing issues, enter a JQL under Rebuild these issues (JQL) and click Rebuild fields now. The rebuild runs in the background and only writes values that changed.
Free syncs one field. Standard syncs up to 100. If a Standard licence lapses, only the first mapping keeps running.
Team-managed projects: Jira only accepts a value for a field that is on the issue's work type, and a site-wide field is not on a team-managed project's work types until a project admin adds it under Project settings → Work types (Jira only offers fields with a global context). Linger can't add it for you, because Jira has no API for team-managed field layouts. You can also map a Number field created inside the team-managed project. It shows as (team-managed: KEY), and Linger writes it on that project's issues only.
CSV download
After a report runs, download Summary CSV, Per-issue CSV, Group-by CSV, Assignee CSV or, on Standard, Sprint CSV.
Charts and insights
On the Reports page (Statuses tab): average or P85 working time per status, so the bottleneck shows at a glance, and a stacked bar of time per status for the 10 slowest issues — both free. The issue panel shows a small bar of time per status. Standard adds a cycle-time trend: P50 and P85 per week or month.
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.
Free vs Standard
Plans and prices below are read from the same pricing file the app uses. Atlassian bills per user per month on your site's user tier, and the price per user steps down at larger tiers. See all pricing.
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)
Standard
$0.60 / user / month
Free for sites up to 10 users. 30-day free trial.
- Reports up to 50,000 issues each (free stops at the 1,000 most recently updated)
- Time in status per sprint (working time inside each sprint's dates)
- Working calendars for up to 50 projects (free: 1); the rest use the site calendar
- Copy time in status into up to 100 number custom fields (free: 1)
- Per-status and per-status-group SLA targets, 100 saved reports
- Stuck-work flags inside Jira, searchable with JQL (lingerStuck = "yes")
- Optional stuck alerts: one Jira comment @mentioning the assignee or watchers
- Per-issue CSV of every issue in the report
- Everything in Free
Limits
- Free reports cover the 1,000 most recently updated issues that match (one project or any JQL); the free gadget covers one project's 1,000 most recently updated issues.
- Standard JQL reports stop at 50,000 issues per run; the page says so if that safety stop is reached.
- The per-issue CSV covers the first 10,000 issues of a report; narrow the JQL for the rest.
- Saved reports: 5 on Free, 100 on Standard.
- Stuck-work flags update hourly. In a scope with more than 2,000 open issues, the 2,000 least recently updated are checked each run.
- Stuck alerts: at most 25 comments per hourly run, up to 10 people @mentioned per comment, one comment per stay in a status, and no repeat for 30 days if the issue returns to that status.
- Up to 20 status groups, 50 status-specific targets and 200 holidays.
- Project calendars: 1 on Free and up to 50 on Standard, on top of the site calendar. If a Standard licence lapses, the first project calendar (by project key, A–Z) keeps applying; the others are kept, not deleted, and apply again on Standard.
- Field sync: number custom fields only, 1 mapping on Free and 100 on Standard. In a team-managed project the field must be on the work type (added by a project admin) or be that project's own field. Time still running in the current status is refreshed at the next status change or rebuild, not continuously. A rebuild writes about 4 issues a second and stops at 50,000 issues.
- The issue panel's transition list shows the latest 200 stays; earlier ones are counted but not listed.
Data & privacy
What Linger 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 into Linger.
- Forge hosted storage, kept per Jira site: the working calendar, project calendars (project key and hours only), settings (default and per-status targets, status groups and their targets, the stuck-flag JQL scope and alert option), saved report setups (names and scopes), counts from the last flag run, field-sync mappings and counts from the last field rebuild, cached aggregate report figures (no assignee data), the sprint field id and a random key used to sign report pages.
- For stuck alerts: issue key, status and time per alert, so the same stay is not commented on twice. The people to @mention are read from the issue when the comment is posted and are not stored.
- On issues: the
linger-stuckproperty (status name, working days in status, target and when it was flagged, no account IDs) when stuck-work flags are on, and one comment per stuck stay when stuck alerts are on. - In the number custom fields an admin maps in field sync: the working time in the chosen status.
- Assignee names are read from Jira to show time per assignee in your browser; Linger does not store them.
- The app declares no external egress, so no data is sent to servers outside Atlassian.
Linger 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)
| Scope | Why Linger needs it |
|---|---|
read:jira-work | Read issues, their changelogs, statuses, projects and sprints to calculate time in status. |
write:jira-work | Only to set or remove the linger-stuck issue property, when stuck alerts are on to add one comment per stuck stay, and to write the number fields an admin maps in field sync. Linger never edits any other field, transitions issues, edits or deletes comments, or creates issues. |
storage:app | Keep the calendar, settings, saved reports and flag history in Forge hosted storage. |
FAQ & troubleshooting
Why do the times look longer or shorter than I expected?
The main figure is working time on the site calendar, not clock time. If no admin has set the calendar, Linger uses Mon–Fri, 09:00–17:00 UTC. Ask a Jira admin to set your timezone, hours, working days and holidays with Edit calendar on Linger Reports. The clock time is shown beside each figure for comparison.
Why does my report stop at 1,000 issues?
Free reports run on one project or any JQL, across projects and date ranges, and cover the 1,000 most recently updated issues that match. Standard raises that to 50,000 issues per run.
Why can't I edit the calendar, SLA targets or flags?
Only Jira admins can change them. Other users see the current settings on the Reports page.
How do I find stuck issues in Jira?
On Standard, turn on stuck-work flags and give a JQL scope. Then search with lingerStuck = "yes", for example in a filter, a board or an Automation rule. Flags update every hour, or straight away with Check for stuck work now.
I turned on stuck alerts but no comments appeared. Why?
Alerts only go out for issues newly flagged after you turn them on; issues already stuck get no comment. Each stay in a status gets one comment, with no repeat for 30 days, and each hourly run posts at most 25 comments.
Why is the By sprint tab empty?
Time in status per sprint is a Standard feature and needs Jira Software's sprint field. If the site has no sprint field, or no issue in the scope was in a started sprint, there is nothing to show.
Does Linger change my issues?
Not unless an admin sets it up: field sync writes the number fields the admin maps (free, off until a mapping is added), stuck-work flags set the linger-stuck issue property, and stuck alerts post one comment per stuck stay (both Standard, off by default).
Is there a free version of Linger?
Yes. Linger has a Free plan, and Linger Lite is a separate, always-free app with exactly Linger's free features and no licence or trial at all.
Why didn't my synced field change?
Linger updates it when the issue changes status, and only if the field is on that issue's screen and project. Time still running in the current status is refreshed at the next status change; run Rebuild fields now to refresh everything. On Free only the first mapping runs.
Changelog
Every release and what changed: Linger 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.