Getting Started

Assets Quality Guard helps Jira Service Management administrators find incomplete, stale, or risky Assets records before those records break request forms, imports, automations, reports, or audit workflows.

The app is read-only for Assets data. It scans your Assets schemas and objects, stores compact finding evidence, and gives your team a remediation queue without creating, editing, or deleting CMDB records.

Before you start

You need:

A Jira Service Management Cloud site with Assets available.
Jira site administration access so you can install and open apps from Jira admin settings.
Permission for the app to read Assets workspaces, schemas, object types, attributes, and objects.
At least one Assets schema with object types you want to monitor.

Assets Quality Guard runs inside Forge and does not require external data connections for the MVP.

Install the app

Install Assets Quality Guard on the Jira site that contains your Assets workspace. After installation, open Jira administration and find Assets Quality Guard under the Apps navigation.

If your site asks for an app upgrade after new scopes are added, approve the upgrade before continuing. The app needs read-only CMDB scopes to discover metadata and run scans.

Refresh Assets metadata

Start by caching the shape of your Assets data:

Open Assets Quality Guard from Jira admin Apps.
Go to Settings.
Select Refresh Assets metadata.
Wait for the refresh job to finish.

The metadata refresh discovers the Assets workspace, schemas, object types, and attributes the app can read. The Settings page shows the last refresh time plus discovered schema, object type, and attribute counts.

If the refresh fails, check that the app is installed on the right Jira site and that it has the required Assets read permissions.

Create your first policy

Policies tell the scan what “good enough” means for an object type or schema.

Go to Policies.
Select Create policy.
Choose a built-in preset, or build a policy from scratch.
Choose the schema and object type you want to monitor.
Select the workflow impact area, such as request portal, import and sync, automation and AQL, reporting and export, audit and change, or general CMDB hygiene.
Save the policy.

For a quick first policy, choose CMDB trust baseline for an important object type. It checks common ownership, lifecycle, identifier, and freshness signals.

Use object-type policies when you need attribute-backed checks such as required attributes, relationship integrity, or import readiness. Use schema policies when you only need stale-object coverage across every object type in a schema.

Run your first scan

After metadata and at least one enabled policy are ready:

Go to Dashboard.
Select Start scan.
Watch the current scan status and progress.
Open Scan history if you need the job status, duration, scanned object count, finding count, or error summary.

The app also includes a daily scheduled scan. Scheduled scans run only after discovery is ready and no other scan is active.

Review findings

Open Findings to prioritize remediation work.

Each finding includes severity, finding type, schema, object type, object key or label, evidence, recommended remediation, and workflow impact. Use filters to focus on a specific severity, status, schema, object type, finding type, or impact area.

When a finding no longer needs active remediation, mark it resolved or ignored. Repeated scans update existing findings instead of creating duplicates.

Export a remediation queue

Use Export remediation CSV from the Dashboard or Findings page when another team needs a cleanup list.

The export includes the finding ID, Assets workspace ID, severity, status, workflow impact, schema, object type, object key, object label, affected attribute, evidence, recommendation, and first and last seen timestamps.

Common blockers

No metadata yet: Refresh Assets metadata from Settings before creating policies or starting a scan.
Start scan is disabled: Make sure metadata is ready and at least one policy is enabled.
Policy attributes are missing: Refresh metadata again after changing Assets object types or attributes.
Scheduled scans are not producing results: Confirm discovery has completed and that the Marketplace license is active.
Permission or availability errors: Recheck the app installation, app scopes, and Assets availability on the Jira site.