Checks
In short
The Checks page is where you understand your Solcoro Score: the overall governance score at the top, the three category scores beside it, and below them the full list of checks that roll up into those numbers. Every check is interactive: click into one to see the specific items it flagged, read why they matter, and jump into the matching Explore surface to investigate.
Before you begin
A connected integration with at least one completed scan; the page has nothing to show until a scan has run.
How the page is organized
Three sections, top to bottom: the score cards, the controls (search, filters, export), and the checks list.
The scan selector
The Select Scan dropdown controls which scan the page shows; by default, the most recent. Switching to an older scan refreshes everything: every score, count, and check status updates to that scan. Use it to compare posture over time: open last month's scan, note the score, switch back.
Reading the Solcoro Score
The first card shows the Solcoro Score as a 0–100 gauge. Higher is better: it is a blended index aggregating every check, weighted by severity and calibrated against instances of similar size. The About Scoring link in the card opens the full model.
Reading the three category scores
Category | What it measures |
|---|---|
Configuration Score | How tidy the instance setup is: orphans, duplicates, draft workflows, fields without screens or contexts. A drop means it is time for a cleanup pass |
Usage Score | How Jira feels day to day: the patterns that create friction users hit and admins rarely see |
Compliance Score | Where the instance is exposed to security, audit, or continuity risk. A drop here is the one to address first: these are the items that surface in audits and incidents |
The categories are not independent: many checks contribute to more than one (tagged, for example, "Usage, Configuration"), so improving one check can move multiple numbers at once.
Using the checks list
Every check Solcoro ran on the scan, in five columns:
Column | What it shows |
|---|---|
Check | The check name. Click to open the check's detail |
Type | The category or categories it contributes to |
Score | The check's contribution to your Solcoro Score. Higher means it is pulling the score down more; 0 means it is not currently moving the score materially |
Count | How many items it flagged on this scan |
Status | Fail, Risk, or Pass |
Default sort is by Status, so Fail results surface first. Checks are also tagged by the configuration object type they examine, which keeps the list navigable by domain.
Reading the Score column
A check's Score is size-relative: the same finding counts for more in a smaller instance. A Score of 0 does not mean the check found nothing; it means what it found is not materially moving your score, typically because the count is small relative to instance size or the items are low severity. Count is how many; Score is how much it matters for your instance.
Filters, search, and export
Filter by status narrows to Fail, Risk, or Pass: filter to Fail for triage. Filter by type narrows by category: filter to Compliance to see everything affecting that score. Search matches check names ("field" finds every field check). Export all checks downloads the whole list; per-check export lives inside each check's detail.
Opening a check
Click a check name for the full picture:
Section | What it contains |
|---|---|
Title and Score | The check's name and its contribution to your score |
Description | The pattern or configuration state the check looks for |
Why This Matters | The practical consequences for your instance |
Export | Downloads just this check's items |
Item list | Every specific item flagged on this scan |
Every check also has a full reference page in the Check Reference covering investigation questions, remediation steps in Jira, and how to watch the check with Pulse and Drift.
The item list
The specific flagged items, with columns tailored to the check: a field check might show Id, Name, Field Type, Locked, Screens Count, Context Count; an issue type check shows hierarchy and scheme membership. Long lists paginate.
Jumping into Explore
Where an Explore surface exists for the item type, the Id column links straight to that item's detail view: field items open in Fields, workflows in Workflows, screens in Screens. Item types without an Explore surface yet are unlinked; as surfaces ship, their items become clickable. The rule: if Solcoro has a place to show you the item in detail, the list links to it.
Frequently asked questions
Why does a check show Score 0 with 40 items in its Count?
Size relativity. Forty items in a very large instance can be negligible; the same forty in a small instance would score high. Count is volume; Score is materiality for your instance.
Why are some checks tagged with two categories?
Because they genuinely affect both dimensions. Fields with no screens is both a Usage problem (users cannot fill in what they cannot see) and a Configuration problem (clutter). Multi-tagged checks contribute to each category they carry.
Why can I click some items but not others?
Clickable items have an Explore surface built for their type. Fields, workflows, and screens do; item types without a surface yet are plain text until theirs ships.
Why is my Solcoro Score not the average of the three categories?
It is a weighted blend, not an average: each category contributes differently, calibrated for instance size. Three category scores in the mid-50s can produce an overall score a point or two away from their average.
What's next
Check Reference — every check's full page: detection, remediation, and monitoring guidance
About Scoring — the scoring model in full
Explore — investigating flagged items domain by domain
Compare Scans — how check results moved between any two scans