QA Issue Types
Create and manage Quality Assurance Issue Types used to categorize problems identified during QA Reviews.
QA Issue Types provide a consistent way to categorize problems identified during Quality Assurance Reviews in Monolith.
Organizations can define Issue Types that reflect the kinds of exceptions, deficiencies, or review findings they want to track.
Examples might include:
Compliance
Data Acquisition
Documentation
Tool Validation
Process Deviation
Reporting
Policy or SOP Violation
Other organization-specific quality issues
View QA Issue Types
The QA Issue Types settings page displays the Issue Types currently configured for your organization.
Each Issue Type also shows the number of QA entries currently associated with it.
Use this list to review the classifications available when documenting issues found during a QA Review.

Create a QA Issue Type
To create a new QA Issue Type:
Select Create Type.
Enter the name of the new Issue Type.
Select Create Issue Type to save it.
The new Issue Type becomes available for supported Quality Assurance workflows throughout Monolith.
Choose names that clearly describe the type of problem being documented.

Using QA Issue Types
QA Issue Types help standardize how review findings are categorized.
For example, a reviewer may identify an issue related to:
Evidence handling
Acquisition methodology
Missing documentation
Report content
Tool validation
Internal procedure
Compliance requirements
Using consistent Issue Types makes it easier for teams to distinguish between different kinds of QA findings rather than relying only on free-text descriptions.
QA Issue Types and QA Reviews
QA Issue Types are used as part of the Case-level Quality Assurance workflow.
During a QA Review, reviewers can document issues identified while checking work against the appropriate QA Checklist.
This allows the review record to preserve both:
The checklist or review process being performed
The type of issue identified during that review
See QA Checklist Items for information about creating reusable Quality Assurance review checklists.
Delete a QA Issue Type
QA Issue Types can be deleted when they are no longer needed.
Before deleting an Issue Type, review whether it is still being used by existing QA records and whether the classification should remain available for future reviews.

Recommended Practices
Create Issue Types that represent meaningful categories of QA findings.
Keep names clear and consistent across the organization.
Avoid creating duplicate or overlapping Issue Types.
Use categories broad enough to remain useful across multiple review workflows.
Review Issue Types periodically as quality procedures and organizational requirements change.
Coordinate QA Issue Types with your QA Checklists so reviewers have consistent ways to classify findings.
Related Documentation
Last updated
Was this helpful?