Issue
User Guide — Track, Investigate, and Resolve Data Quality Issues
| Last updated: September 2026
Contents
- Overview
- Finding Your Way Around
- The Issue List
- Creating an Issue
- Investigating the Cause — Root Cause Analysis
- Recording a Resolution
- Quick Reference
1. Overview
The Issue screen is where data quality problems are tracked from the moment they're spotted to the moment they're fixed. When a rule fails, that failure becomes an issue you can see, investigate, and close off — with a record of what went wrong, why, and how it was resolved.
Issues arrive in two ways: many are raised automatically when a rule fails during scoring, and you can also add one by hand when you notice a problem yourself. Either way, the screen gives you one place to manage them and keep an audit trail.
What you can do here
- See all your data quality issues and search for the ones you want.
- Add an issue manually.
- Record a Root Cause Analysis — what caused the issue.
- Record a Resolution — how it was dealt with.
- Delete issues you no longer need to track.
WHERE TO FIND IT — Open Quality → Issue.
2. Finding Your Way Around
The Issue screen is built around one main list and two linked screens you open for a single issue:
- Issue list — every issue in a searchable table. This is where you start.
- Root Cause Analysis — opens for one issue, to record what caused it.
- Resolution — opens for one issue, to record how it was resolved.
You reach Root Cause Analysis and Resolution from the buttons on each issue's row (see below). Both have a button to return to the issue list when you're done.
3. The Issue List
The Issue list shows every issue in a table, with a search bar at the top to narrow it down and a plus (+) button in the bottom-right to add one.
Each row is one issue. The columns are:
| Column | What it shows |
|---|---|
| Action | The first column on the left, holding the buttons for each issue — Root Cause Analysis, Resolution, and Delete (see below). |
| Catalog Name | The dataset (table) the issue relates to. |
| Rule Name | The rule that raised or applies to the issue. |
| Business Attribute | The data element involved. |
| Dimension | The quality dimension the issue falls under. |
| Status | Where the issue stands — for example open or closed. |
| Issue Date | The date the issue applies to. |
| Initial As Of Date | The reporting date the issue was first seen on. |
| System Created | Ticked when the issue was raised automatically by a failing check (rather than added by hand). |
| Root Cause | The cause recorded for the issue, once known. |
| Date Reported | When the issue was reported. |
| Method Closed | How the issue was closed, once it is. |
| Updated By / Updated Date | Who last changed the issue, and when. |
Searching. Use the search bar to filter the list — for example to a particular rule, catalog, or status — and clear it to return to the full list.
Each row's actions. In the Action column — the first column on the left of every row — you'll find:
- Root Cause Analysis — opens that issue's analysis screen (see below).
- Resolution — opens that issue's resolution screen (see below).
- Delete — removes the issue after you confirm.
SYSTEM-CREATED ISSUES COME FROM YOUR RULES — When System Created is ticked, the issue was raised automatically because a rule failed during scoring. These link your Scorecard results directly to the issues they cause, so nothing slips through unnoticed.
4. Creating an Issue
Most issues are raised for you, but you can add one yourself with the plus (+) button. This opens the Create Issue dialog. Fill in the fields and save.
| Field | What to enter |
|---|---|
| Catalog Name | The dataset (table) the issue relates to. |
| Rule Name | The rule the issue is about. |
| Business Attribute | The data element involved. |
| Dimension | The quality dimension it falls under. |
| Issue Date | The date the issue applies to. |
| Initial as of Date | The reporting date it was first seen on. |
| Root Cause | The cause, if you already know it (you can add this later instead). |
| Date Reported | The date the issue was reported. |
Once saved, the issue appears in the list alongside the automatically raised ones.
5. Investigating the Cause — Root Cause Analysis
To record why an issue happened, open its Root Cause Analysis from the issue's row. This screen keeps a list of analysis entries for that one issue, so you can capture your investigation as it develops.
Use the plus (+) button to add an entry:
| Field | What to enter |
|---|---|
| Analysis Detail | A description of what you found — the cause, or your working notes. |
| Resolution Type | The kind of fix the cause points to. |
You can add more than one entry, delete any that no longer apply, and use the return to issue button to go back to the list.
WRITE IT DOWN WHILE IT'S FRESH — A clear analysis note is what stops the same problem being investigated from scratch next time it appears.
6. Recording a Resolution
To record how an issue was dealt with, open its Resolution from the issue's row. Like Root Cause Analysis, this keeps a list of entries for that one issue.
Use the plus (+) button to add a resolution:
| Field | What to enter |
|---|---|
| Resolution Description | What was done to resolve the issue. |
| Resolution Date | When it was resolved. |
| Resolution Status | The state of the resolution — for example in progress or complete. |
You can add more than one entry, delete any you don't need, and use the return to issue button to go back.
THE FULL STORY IN ONE PLACE — Between the issue itself, its root cause analysis, and its resolution, you keep an end-to-end record: what the problem was, why it happened, and how it was fixed.
7. Quick Reference
A fast lookup for the most common actions.
| I want to… | Do this |
|---|---|
| See all data quality issues | Open Quality → Issue |
| Find a particular issue | Use the search bar at the top of the list |
| Tell auto-raised issues from manual ones | Look at the System Created column |
| Add an issue myself | Select the + button and complete the Create Issue dialog |
| Record what caused an issue | Open its Root Cause Analysis, add an entry |
| Record how an issue was fixed | Open its Resolution, add an entry |
| Remove an issue | Use the delete action on its row |
| Go back from an analysis or resolution | Select return to issue |
Source: OnCoor Quality module product documentation, written for end users. For the latest screens and options, always refer to the in-app interface.