User Cleanup
Scan users and groups
To scan users and groups:
[管理] > [システム] の順に移動します。
サイドバーで [Instance Optimizer] を選択します。
Open User cleanup.
Click Run Scan.
The scan creates a point-in-time result set. After disabling or deleting rules, run a new scan to refresh the results.
スキャンでは、次のような推奨事項に一致するルールがチェックされます。
推奨事項 | 説明 |
|---|---|
Total users per instance | User counts exceeding 1M per instance |
Potentially inactive users | Users that have not logged in for more than 6 months |
Bot accounts | Helps identify bot accounts and their recent activities |
Never logged-in users | Users that were created older than 6 months that have never logged in |
Duplicate accounts | Accounts that share an email address with at least one other account. |
| Total users per group | Groups that have a user count of over 290,000 |
| Groups with no users | Groups that don't have any users |
| Groups with potentially no active users | Groups that only have users that haven't logged in for more than 6 months |
Total groups per directory | Groups exceeding 250k per directory |
Directories with no users | Directories that don't have any users |
| Directories with potentially no active users | Directories that only have users that haven't logged in for more than 6 months |
制限を設定する
User cleanup uses default limits to identify users that may need review.
limit | 既定値 |
|---|---|
Inactive months | 6 |
Created months | 6 |
Bot groups and patterns | 空 |
Groups per directory | 250k |
合計ユーザー数 | 1M |
Users per group | 290k |
To change these limits, open User cleanup, then select Configure User cleanup.
Configure bot identification
Bot identification tells User cleanup which accounts are service or automation accounts, so they surface under the Bot accounts recommendation instead of looking like ordinary inactive users. No account is treated as a bot until you add at least one rule.
To set it up, open User cleanup, select Configure User cleanup, then use the Bot identification section.
There are two kinds of rules, and an account is flagged if it matches either one:
ルール | 説明 |
|---|---|
Bot groups | Accounts belonging to listed Jira groups. Search and add groups by name (max 100). |
Bot username patterns | Regular expressions matched against each account’s username and display name. (max 25) |
A pattern matches anywhere in the name unless you anchor it, so svc- also matches mysvc-1. Use ^svc- to match only names starting with svc-, or -bot$ for names ending in -bot.
Select Save bot identification to apply your changes. Bot rules are read when a scan starts, so run a new scan to see the effect. Results from earlier scans don’t change.
Apart from bot identification configuration, we don’t recommend adjusting default limits in production instances without consulting Atlassian support. The default limits are optimized for performance.
結果の確認とフィルタリングを行う
After a scan finishes, Instance optimizer shows the matching users and the top recommendations.
次のような条件で結果をフィルタリングできます。
ユーザ名
ステータス
ディレクトリ
- グループ
License
- Optimization area
- Last active
Directory and group filters
The Group filter becomes available after you select a directory. It initially shows up to 20 suggested groups for the selected directory. To find a group that is not in the suggestions, type in the filter and search by group name. You can select multiple groups to narrow the results.
Bulk actions - Users
You can select up to 1,000 users for cleanup at a time. Selected users can be deactivated, deleted, anonymized or reactivated.
Before deactivating, deleting or anonymizing users, we recommend exporting them to a CSV file. Deleted users can't be recovered from Instance optimizer.
To change the maximum cleanup count, set this property in your Jira home directory’s application property file, then restart Jira: jira.optimizer.plugin.user.cleanup.bulk.action.max.users. The value is capped at 5,000 per cleanup.
Bulk actions - Groups and Directories
You can select up to 1,000 Groups and Directories for cleanup at a time. Selected groups can be deleted, and selected directories can be disabled.
Before deleting groups or disabling directories, we recommend exporting them to a CSV file. Deleted groups can't be recovered from Instance optimizer. Disabled directories can be re-enabled on the User Directories page.
To change the maximum cleanup count, set this property in your Jira home directory’s application property file, then restart Jira: jira.optimizer.plugin.user.cleanup.bulk.action.max.directories or jira.optimizer.plugin.user.cleanup.bulk.action.max.groups. The value is capped at 5,000 per cleanup.
監査ログ
A cleanup action adds audit log entries when the cleanup starts and when it completes. It also records change of ownership of projects or components when applicable.
Scheduled scans
User cleanup includes a preconfigured scan schedule:
タスク | デフォルト スケジュール |
|---|---|
スキャン | 毎週日曜日の午前 3:00 |
スケジュールを更新するには、Jira ホーム ディレクトリのアプリ プロパティ ファイルに次のプロパティを設定して、Jira を再起動します。
jira.user.cleanup.scan.cron controls the scheduled scan cron.
By using a cron expression, you can specify exactly when the scan occurs. For example, the default value 0 0 3 ? * SUN schedules user cleanup scan every Sunday at 3:00 a.m.