Getting started

How Seatwise decides a seat is unused

Seatwise looks at each person's last Jira work, not their last login. You choose how long without Jira work counts as unused.

ForJira admins

Before you startSeatwise has finished its first check.

  1. Last Jira work means creating, editing, moving or commenting on work items, or logging time.
  2. Viewing Jira does not count. Someone who only reads Jira can look unused.
  3. Seatwise shows a range, not a date: “In the last 30 days”, “90+ days”, “180+ days”, “365+ days” or “Never”.
  4. Each person's details say when this was checked, for example “From Jira (checked 13 Oct)”.
  5. To change the limit, open Settings, then “When a seat counts as unused”. Choose 90 days, 180 days or 365 days.
  6. Then choose “Save settings”. The lists and Home use the new limit.
  7. If Jira can't answer for a person, Seatwise counts them as active. It never suggests removing someone on a guess.
  8. Seatwise rechecks people who look unused in the background. Someone who starts working again drops off the list.
  9. For exact “last seen” dates, add Atlassian's user export.

What you should see

The “No Jira work in 90+ days” list (or 180+ or 365+) shows only people with no Jira work for that long.

If something is not right

Someone who reads Jira every day shows as unused. Reading doesn't count as Jira work. Add Atlassian's user export, which has the last-seen date. People seen within your chosen time then drop off the cleanup list.

The list didn't change after you picked 180 days. Choose “Save settings” at the bottom of Settings. Until you do, the bar says “You have changes that are not saved.”

Still stuck? Write to [email protected].