Create an Issue form
Use the Create an Issue form in GRC: Compliance Case Management to add an issue to a compliance case, report findings or observations or compliance deficiencies, or matters that require immediate attention from the respective owners.
For a description of the field values, see the following table.
|
Field |
Description |
|---|---|
|
Issue | |
|
Number |
Number of the issue. This field is automatically filled in. |
|
Name |
Name of the issue. |
|
Issue source |
Source of the issue, such as Compliance Case analysis. This field is automatically filled in. |
|
Issue type |
Issue Type is a way of classifying the nature of issue being reported. This field is automatically filled with one of the following options based on how the issue was created:- Control design effectiveness failure
|
|
Classification |
Classification of the issue. This field is automatically filled in with one of the following options:- Audit
|
|
Location |
Location of the issue. |
|
State |
State of the issue:- New
|
|
Substate |
Substate of the issue is the sub-type of the issue. This field is automatically filled in. |
|
Priority |
Priority of the issue:- Critical
|
|
Issue rating |
Rating of the issue:- Very High
|
|
Description |
Approver of the issue. |
|
Assignment | |
|
Assignment group |
Assignment group for the issue. For example, Compliance team or Ethics/ Compliance team. |
|
Assigned to |
User that the issue is assigned to. |
|
Issue manager group |
User assigned to work on the recorded issue:- Compliance Managers
|
|
Issue manager |
Manager that the issue is assigned to. |
|
Watchlist |
Users who are on the watchlist for the issue. |
|
Schedule | |
|
Due date |
Date when the issue is due. |
|
Confirmed date |
Confirmation date for the issue. This field is automatically filled in based on the auto-calculation of future dates. |
|
Planned start date |
Planned start date for the issue. |
|
Planned end date |
Planned end date for the issue. |
|
Duration |
Duration for the issue in days, hours, minutes, and seconds. |
|
Created |
Date on which the issue is created. This field is automatically filled in based on the current system date. |
|
Closed |
Date on which the issue is closed. |
|
Actual start date |
Actual start date for the issue. |
|
Actual end date |
Actual end date for the issue. |
|
Actual duration |
Actual duration for the issue in days, hours, minutes, and seconds. |
|
Issue grouping | |
|
Parent issue |
Parent issue associated with this issue. |
|
Issue group rule |
Group rule for the issue. This field is auto-populated. |
|
Action plan | |
|
Recommendation |
Recommendation for the issue. |
|
Action plan |
Action plan for the issue. |
|
Activity | |
|
Work notes |
Work notes for the issue. |
|
Additional comments |
Additional comments for the issue. |
|
Settings | |
|
Functional domain |
Functional domain for the issue. |
Apart from the from fields, there are a few actions that you can perform on a Compliance Case record.
- Attachment- select this icon in the side-bar to add any related attachments to the Compliance Case record.
- Compose email- compose an email.
- Discard draft- discard a draft version of the email.
- Send email- send the email with all the details in it.
- Create new email- Create a new email.
- View drafts - view the existing drafts in the system.
- Save- save the details of the compliance case.
- 360 view- view the compliance case in a 360 view with all the relationships.
- Export PDF- export the compliance case as a PDF.
- Delete- delete the compliance case.
Parent Topic:Add an issue for a compliance case
--- title: Create an Issue form description: Use the Create an Issue form in GRC: Compliance Case Management to add an issue to a compliance case, report findings or observations or compliance deficiencies, or matters that require immediate attention from the respective owners. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/compliance-case-management/create-issue-compliance-ws.html release: australia product: Compliance Case Management classification: compliance-case-management topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 3 breadcrumb: [Add issue, Use, Compliance Case Management, Governance, Risk, and Compliance] --- # Create an Issue form Use the Create an Issue form in GRC: Compliance Case Management to add an issue to a compliance case, report findings or observations or compliance deficiencies, or matters that require immediate attention from the respective owners. For a description of the field values, see the following table. <table id="table_FloorForm"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td class="sub-head" colspan="2"> Issue </td></tr><tr><td> Number </td><td> Number of the issue. This field is automatically filled in. </td></tr><tr><td> Name </td><td> Name of the issue. </td></tr><tr><td> Issue source </td><td> Source of the issue, such as Compliance Case analysis. This field is automatically filled in. </td></tr><tr><td> Issue type </td><td> Issue Type is a way of classifying the nature of issue being reported. This field is automatically filled with one of the following options based on how the issue was created:- Control design effectiveness failure - Control operative effectiveness failure - Control doesn’t meet requirement - Control doesn’t exist - Non-compliance to a regulation - Non-compliance to a policy - Improvement or suggestion to an existing policy - Recommendation for a new policy - Process optimization or improvement - Observation - Data breach - Fraud - Misstatement - Training - Documentation </td></tr><tr><td> Classification </td><td> Classification of the issue. This field is automatically filled in with one of the following options:- Audit - Compliance - Operational Resilience - Risk - Vendor </td></tr><tr><td> Location </td><td> Location of the issue. </td></tr><tr><td> State </td><td> State of the issue:- **New** - **Analyze** - **Respond** - **Review** - **Closed Complete** - **Closed Incomplete** </td></tr><tr><td> Substate </td><td> Substate of the issue is the sub-type of the issue. This field is automatically filled in. </td></tr><tr><td> Priority </td><td> Priority of the issue:- **Critical** - **High** - **Moderate** - **Low** - **Planning** </td></tr><tr><td> Issue rating </td><td> Rating of the issue:- **Very High** - **High** - **Moderate** - **Low** - **Very Low** </td></tr><tr><td> Description </td><td> Approver of the issue. </td></tr><tr><td class="sub-head" colspan="2"> Assignment </td></tr><tr><td> Assignment group </td><td> Assignment group for the issue. For example, Compliance team or Ethics/ Compliance team. </td></tr><tr><td> Assigned to </td><td> User that the issue is assigned to. </td></tr><tr><td> Issue manager group </td><td> User assigned to work on the recorded issue:- **Compliance Managers** - **IT Risk Managers** - **Risk Managers** </td></tr><tr><td> Issue manager </td><td> Manager that the issue is assigned to. </td></tr><tr><td> Watchlist </td><td> Users who are on the watchlist for the issue. </td></tr><tr><td class="sub-head" colspan="2"> Schedule </td></tr><tr><td> Due date </td><td> Date when the issue is due. </td></tr><tr><td> Confirmed date </td><td> Confirmation date for the issue. This field is automatically filled in based on the auto-calculation of future dates. </td></tr><tr><td> Planned start date </td><td> Planned start date for the issue. </td></tr><tr><td> Planned end date </td><td> Planned end date for the issue. </td></tr><tr><td> Duration </td><td> Duration for the issue in days, hours, minutes, and seconds. </td></tr><tr><td> Created </td><td> Date on which the issue is created. This field is automatically filled in based on the current system date. </td></tr><tr><td> Closed </td><td> Date on which the issue is closed. </td></tr><tr><td> Actual start date </td><td> Actual start date for the issue. </td></tr><tr><td> Actual end date </td><td> Actual end date for the issue. </td></tr><tr><td> Actual duration </td><td> Actual duration for the issue in days, hours, minutes, and seconds. </td></tr><tr><td class="sub-head" colspan="2"> Issue grouping </td></tr><tr><td> Parent issue </td><td> Parent issue associated with this issue. </td></tr><tr><td> Issue group rule </td><td> Group rule for the issue. This field is auto-populated. </td></tr><tr><td class="sub-head" colspan="2"> Action plan </td></tr><tr><td> Recommendation </td><td> Recommendation for the issue. </td></tr><tr><td> Action plan </td><td> Action plan for the issue. </td></tr><tr><td class="sub-head" colspan="2"> Activity </td></tr><tr><td> Work notes </td><td> Work notes for the issue. </td></tr><tr><td> Additional comments </td><td> Additional comments for the issue. </td></tr><tr><td class="sub-head" colspan="2"> Settings </td></tr><tr><td> Functional domain </td><td> Functional domain for the issue. </td></tr></tbody> </table>## Other actions Apart from the from fields, there are a few actions that you can perform on a Compliance Case record. - Attachment- select this icon in the side-bar to add any related attachments to the Compliance Case record. - Compose email- compose an email. - Discard draft- discard a draft version of the email. - Send email- send the email with all the details in it. - Create new email- Create a new email. - View drafts - view the existing drafts in the system. - Save- save the details of the compliance case. - 360 view- view the compliance case in a 360 view with all the relationships. - Export PDF- export the compliance case as a PDF. - Delete- delete the compliance case. **Parent Topic:**[Add an issue for a compliance case](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/compliance-case-management/add-issues-for-compliance-case.md)
This file has no frontmatter.