Leavers and groups

Hand over what leavers own

People who left can still own filters, dashboards, spaces they lead and open work items that others rely on. Pick a new owner and hand it all over in one click. Seatwise lists what you change by hand.

ForJira admins

Before you startSeatwise has finished a check. The person who left has a deactivated account. Seatwise lists them only while they still own something. Your Seatwise license is active.

  1. On Home, choose “Hand them over” in “Leftovers from people who left”. Or open People, then “Left, still own things”.
  2. The list shows each person who left, when they left and what they still own. Choose “Hand over 11” on a row.
  3. Under “New owner”, Seatwise suggests someone when it can. For example, the person subscribed to most of their shared filters.
  4. To pick someone else, choose “Change” and type 2 or more letters of a name. Only people with an active Jira account are shown.
  5. Each time the page opens, Seatwise checks what still belongs to the person. While it checks, the button says “Checking what still belongs to them…”.
  6. The table shows what moves: filters, dashboards, spaces they lead, components they lead, plans they lead and user fields whose default user is them. Each row says what happens after.
  7. Plans exist only on Jira Premium and Enterprise. On other plans, Seatwise names them under “Not checked”.
  8. If they still have open work items, the box “Also assign their … open work items to …” starts ticked. Jira won't send an email for each one.
  9. Untick that box to leave the open work items assigned to them.
  10. Under “Space roles”, the box “Also remove … from these 2 space roles when you hand over” starts ticked.
  11. Untick that box to leave the space roles as they are.
  12. Choose “Hand over 11 things to …”. Everything in the table gets the new owner or the new lead.
  13. Under “Needs you”, Seatwise lists what it can't change, and each row says what to do in Jira.
  14. These are filter subscriptions, permission schemes, notification schemes and work item security levels that name them directly, requests waiting for their approval, and other people's filters whose search names them.
  15. Hand-over has no Undo. To change an owner again, open the item in Jira.
  16. When nothing that others rely on is left with them, the page shows “Ready to delete”. Seatwise never deletes the account. You do that in Atlassian Administration.
  17. Before you delete the account, choose “Download record”. It saves a CSV file of everything they owned and what happened to it. After a delete, their name shows as “Former user”.
  18. Open “Before you deactivate or delete someone” for the steps Seatwise can't do: transfer their automation rules, and find and revoke their API tokens.
  19. History records the hand-over. Seatwise then offers the next person who left.
Hand-over for one person who left: the new owner and what moves. Example data.
Seatwise: Hand-over for one person who left: the new owner and what moves

What you should see

A notice says “Handed over to …”. Each row shows the new owner or the new lead, and the removed space roles. What needs you stays listed with what to do.

If something is not right

A row says “The new owner already has a filter with this name.” Rename one of the two filters in Jira. Then change the owner in that filter's settings in Jira.

You see “Pick someone who still has an active Jira account.” The new owner must have an active account. Choose “Change” and search for someone else.

Search says “Could not search people.” Jira didn't answer. Choose “Try again” next to the message.

The page says “Seatwise couldn't check open work items, component leads and a few other places just now.” Jira didn't answer in time. Choose “Try again” next to the message. Filters, dashboards and spaces can still be handed over.

Open work items show “You need permission to make bulk changes and to edit these work items.” Jira needs you to have the global permission to make bulk changes, and to be allowed to edit those work items. Ask a site admin, then hand over again.

Still stuck? See Troubleshooting, or write to support@unitlane.net.