Documentation

Data Quality scores your Jira projects against configurable data-quality rules and shows you exactly which issues need attention — so gaps get caught before they skew your reports.

Getting started

1. Install Data Quality from the Atlassian Marketplace.
2. Open any Jira Software project and click the Data Quality tab (under "More" if your project has many tabs).
3. Add a rule using the form at the bottom of the page.
4. Click Scan now.

No configuration is required to install the app itself — rules are configured per project, on demand.

How scanning works

Clicking Scan now queues a scan and returns immediately — it does not block the page. The scan runs in the background, paging through your project's issues and evaluating every enabled rule. Once it finishes, the dashboard updates with:

• A score per rule (the percentage of evaluated issues that did not violate it)
• A violations table listing every issue that failed a rule, linked back to the issue in Jira
• The timestamp of the last scan and how many issues were scanned

Automatic scans

Under "Automatic scans" on the project page, you can turn on Weekly or Daily scanning instead of relying on manually clicking Scan now. Automatic scans run on the schedule you choose and update the dashboard the same way a manual scan does.

Trial installations are capped at weekly automatic scans, regardless of what you select here — see Trial limits below.

Rules

Four rule types are available. Every rule can optionally be scoped to specific issue types and, for most rules, specific status categories.

Required field

Flags issues where a specific field is empty. Choose the field from a dropdown of your project's actual fields — for example, requiring Description to be set on every Task.

Orphaned issue

Flags issues (typically Stories) with no parent or epic link. Useful for catching work that's fallen outside your roadmap structure.

Unestimated

Flags issues that are in an active sprint but have no story point estimate. Issues not currently in any sprint are not evaluated by this rule — only in-sprint work is expected to be estimated.

Staleness

Flags issues that haven't had a status change in longer than a threshold you set (in days), while the issue is in an active/in-progress status. Issues already marked Done, or that have changed status recently, are not flagged.

Scoping a rule

Every rule supports:

• Issue types — restrict the rule to specific issue types (e.g. only Task and Story). Leave blank to apply to all issue types.
• Status categories — restrict the rule to To do, In progress, or Done statuses. Leave blank to apply to all statuses.

Enabling and disabling rules

Every configured rule appears in the Rule configuration table with a toggle. Disabling a rule stops it from being evaluated on future scans without deleting its configuration — flip it back on any time.

Trial limits

Trial installations have two automatic limits, enforced regardless of configuration:

• Scan frequency: at most once every 7 days, even if you request daily scans or click Scan now repeatedly.
• Project size: a scan stops after a fixed number of issues rather than scanning an unlimited project.

These limits are lifted automatically once your installation is licensed.

Data retention

Scan results older than 30 days are deleted automatically. Each project's single most recent scan is always kept, so the dashboard never goes empty just because a project hasn't been rescanned recently.

Questions?

See Support for common questions, or email hello@bytloop.com.