Deactivated people and groups

Deactivated people lists the accounts Jira shows as deactivated that still own things or hold permissions. Groups checks the groups your permission schemes grant something to, and lets a Jira admin remove deactivated people from a group.

Before you start

Only Jira admins can open these two pages. Turn on the background checks of Schemes, Filters and Spaces first: Deactivated people adds up what they already read, and it makes no reading of its own. See Getting started.

Deactivated people

The page lists each deactivated account that:

• owns filters or dashboards;
• owns flows, from your last scan;
• is named by a permission scheme;
• leads a space.

Each row says what the account holds and which tool gives it a new owner: Filters, Dashboards or Governance. A permission scheme is changed in Jira. Open an account to see the admin groups it is in (groups a permission scheme gives Administer Projects) and how many other groups.

The page says when Filters last read the owners, because the owners are only as current as that reading. An owner that Jira does not name to you may be a deactivated person.

Deactivated people only reads. It changes no account, group or seat. Only accounts of people are listed, not apps or customers.

Groups

Groups reads the groups your permission schemes grant something to, from Jira, as you. It flags:

• a group that can administer projects and has more than 50 members;
• a group with no member;
• a group Jira no longer has, which a scheme still names;
• deactivated people among the first 50 members.

TuneCraft keeps no group name and no member list.

Remove deactivated people from a group

A Jira admin can remove deactivated people from a group, up to 100 at a time.

1. On Groups, open the group and select Find deactivated members of the group name.
2. Tick the people to remove. The page says about how many points this takes from your hourly budget.
3. Select Remove {n} people from the group (the button shows the number you picked), then confirm with Remove {n} people.

TuneCraft records the removal first. It then checks again, just before it removes each account, that the account is still deactivated and still in the group. You can stop it, and carry on later. Only the group membership changes: TuneCraft never deactivates, deletes or edits an account.

To undo it, open Changes. It adds the people back to the group for 30 days. A trial can remove 10 people.

What it keeps and what it needs

TuneCraft keeps the account ids of the people a permission scheme names, so it can list them. They are erased when an account is closed. It keeps no names or emails.

Groups needs four Jira permissions that earlier versions did not: read and write access to groups, and read access to users and their avatars. A Jira admin approves them when the app is updated. TuneCraft still runs on Atlassian and sends nothing out.

Questions about the app? Write to info@plugincraft.ca.