A ticket is an object in Data Governance and Catalog that either tracks the workflow for a particular asset or can be created to notify the stakeholders of an asset about any issue that may need remediation.
You can create the tickets with or without workflows.
Tickets with workflows
If the administrator has configured workflow approvals, the system creates a ticket when a user attempts to create or modify an asset. After a ticket is created, Data Governance and Catalog starts the workflow that is associated with the asset type. To view all tickets that the system has created for the asset, open the Tickets tab of the asset.
You can use the following types of tickets in the workflow of an asset:
•Approval Request for Create. Use this ticket to start a workflow when you want to create an asset.
•Approval Request for Change. Use this ticket to start a workflow when you want to modify an asset.
The following image shows the Tickets widget with a sample workflow ticket:
Tickets without workflows
When you run rule occurrences on data elements and the validation, completeness, and other parameters are verified, you might receive a poor data quality score for this rule occurrence. You can now create a data quality failure ticket for the issue. The stakeholder of the asset receives a notification after the ticket is created and can start the remediation process.
Create Data Quality Failure tickets to notify the stakeholders of an asset about data quality failure issues.
The following image shows Data Quality Failure tickets that are not associated with a workflow:
When you view the ticket details of a Data Quality Failure ticket on the Tickets tab of an asset page, the Changes section is not visible. This is because no changes are tracked for the tickets that are created without workflows.
