To clean up Assets, you must be logged in as a user with the Jira Administrators global permission. Assets cleanup needs Assets, which comes with Jira Service Management Data Center.

グローバル権限を管理する

Use Instance optimizer to find Assets schemas, object types and objects that exceed recommended limits or are ready for cleanup. Large Assets data can slow Jira down, and cleaning it up first also makes a migration easier.

Assets cleanup scans your Assets data and shows the schemas and object types that match one or more cleanup recommendations. From the scan results, you can review each schema and its object types, export them to CSV, delete schemas and object types you no longer need, remove unique constraints from object types, and delete archived objects.

Scan your Assets data

To scan your Assets data:

1. [管理] > [システム] の順に移動します。

2. In the sidebar, under Instance optimizer, select Assets cleanup. You can also select Manage Assets on the Assets cleanup card of the Instance optimizer dashboard.

3. Select Run scan.

The scan creates a point-in-time result set and only reads your Assets data, so it never changes it. After changing Assets data or the cleanup limits, run a new scan to refresh the results. Only one scan or cleanup action runs at a time across your cluster. If a scan is already running, Instance optimizer shows its progress instead of starting another one.

The scan checks your Assets data against these recommendations:

制限を設定する

Assets cleanup uses default limits to identify Assets data that may need review.

To change these limits, open Assets cleanup, select Configure Assets cleanup, then select Save scan limits. Run a new scan to apply them. Results from earlier scans don't change.
 

本番環境では、アトラシアン サポートに相談せずに既定の制限値を調整することは推奨されません。既定の制限値は、パフォーマンスが最適になるように設定されています。

Review recommendations

After a scan finishes, Instance optimizer shows the recommendations your Assets data matches, three at a time. Use the arrows to see the rest.

Select Apply filter on a recommendation to show only the schemas it counted. The button reads Filter applied while that filter is in place.

The Reduce objects linked to Assets fields on issues recommendation lists each custom field and issue with too many linked objects. Select View custom fields to see the list, along with how many of the linked objects are inactive or archived. Select a field name to open its configuration, or an issue key to open the issue.

Review schemas and object types

Your object schemas are listed on the left, each with its total objects, number of object types and the recommendations it matches.

You can filter schemas by:

• 名前

• Optimization area, for the schema itself or for the object types it contains

• createdDate

You can also sort schemas by total objects, object types, archived objects, attribute types, created date or name.
 

Select a schema to see its details and its object types. The details show when the schema was created, how many objects, archived objects, object types, attribute types and inactive objects it has, and which recommendations its object types match. From here you can open the schema in Assets, export it with Assets import and export, or delete it.

The object type table shows each object type with its place in the hierarchy, its attributes, the recommendations it matches, and its object counts, both its own and in its child object types. Select an object or inactive object count to see those objects in Assets. You can filter object types by name and optimization area.
 

Export results to CSV

You can export the schema list, or the object types of a schema, to a CSV file for review.

To export results:

1. Apply any filters to the schema list or the object type table.

2. Select Export CSV on the schema list or above the object type table.

The export includes every row matching your current filters, in the order shown. Text that starts with =, +, - or @ is prefixed with an apostrophe so spreadsheet apps don't treat it as a formula.

Exports are limited to 250 MB by default. An export can't start while a scan or cleanup action is running. To change the limit, set the jira.optimizer.plugin.assets.cleanup.csv.export.max.bytes property in jira-config.properties, then restart Jira. The limit is capped at 500 MB.
 

バルク アクション

Before deleting any Assets data, we recommend exporting the schema with Assets import and export, or backing up your instance. Deleted schemas, object types and objects can't be recovered from Instance optimizer.

You can select up to 1,000 object types at a time. Only one cleanup action runs at a time, and it can't be cancelled once it has started. Items are processed one at a time, so a problem with one item doesn't stop the rest. When the action finishes, Instance optimizer reports how many items succeeded, failed and were skipped, along with the reason. The latest result stays available if you leave the page and come back.

Each item is checked against your current Assets data before it changes. If an item changed after the scan, it isn't changed and is reported as failed. After a cleanup action, Instance optimizer marks your results as possibly out of date until you run a new scan.
 

Delete a schema

Deleting a schema permanently removes the schema, every object type in it, and all of their active and archived objects. You delete one schema at a time, and Instance optimizer asks you to confirm twice.

Import sources aren't checked. Make sure no import is running on the schema before you delete it.

To delete a schema, select it, select Delete schema, review the counts, then confirm.
 

Delete object types

Deleting an object type permanently removes it, every child object type below it, and all of their active and archived objects. If you select both a parent and its child, the parent's deletion covers the child.

Abstract object types can't be deleted with Assets cleanup, because deleting them would reach their child object types.
 

Remove unique constraints

Removing unique constraints means Assets stops requiring unique values for the selected object types' attributes. Existing values don't change, but new and updated objects can share a value. Child object types lose these constraints too.

Only attributes that belong to the selected object types themselves are changed. Selected object types without unique attributes of their own are left unchanged. To add a constraint back, edit the attribute in Assets.
 

Delete archived objects

Deleting archived objects permanently removes the archived objects of the selected object types. Active objects aren't affected.

To delete archived objects, select object types that have archived objects, select Delete archived objects, then confirm. Each run deletes up to 1,000 archived objects. If there are more, run the action again to delete the rest.

This action needs a Jira Service Management version that can delete archived objects, such as 10.3.27 or later. On earlier versions, Instance optimizer shows that this Assets version can't delete archived objects.

Minimum JSM 11.x version for delete archived objects is 11.3.11.
 

Change the bulk action limit

To change the maximum number of items in one cleanup action, set the jira.optimizer.plugin.assets.cleanup.bulk.action.max.targets property in jira-config.properties, then restart Jira. The limit is capped at 5,000.

監査ログ

Assets cleanup adds entries to the Jira audit log when you change a limit, when a cleanup action starts and completes, and when a CSV export runs. Completed schema and object type deletions record how many object types and objects were affected.

Every entry uses the category Assets cleanup, so searching the audit log for Assets cleanup shows the full history. You can also select For more details see audit logs on the last bulk action banner.