---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Create an Issue form

# Create an Issue form {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

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.
{#create-issue-compliance-ws__table_FloorForm__entry__2}

| 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 * 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 {#create-issue-compliance-ws__ul_slf_znj_xvb} |
| Classification | Classification of the issue. This field is automatically filled in with one of the following options: * Audit * Compliance * Operational Resilience * Risk * Vendor {#create-issue-compliance-ws__ul_cyr_r4j_xvb} |
| Location | Location of the issue. |
| State | State of the issue: * New * Analyze * Respond * Review * Closed Complete * Closed Incomplete {#create-issue-compliance-ws__ul_apn_x4j_xvb} |
| Substate | Substate of the issue is the sub-type of the issue. This field is automatically filled in. |
| Priority | Priority of the issue: * Critical * High * Moderate * Low * Planning {#create-issue-compliance-ws__ul_cfl_fpj_xvb} |
| Issue rating | Rating of the issue: * Very High * High * Moderate * Low * Very Low {#create-issue-compliance-ws__ul_n53_3pj_xvb} |
| 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 * IT Risk Managers * Risk Managers {#create-issue-compliance-ws__ul_yzk_vpj_xvb} |
| 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. |
[Table 1. Create an Issue form]

{#create-issue-compliance-ws__table_FloorForm}

## Other actions {#create-issue-compliance-ws__section_lrh_1qj_2cc}

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.
{#create-issue-compliance-ws__ul_wn1_gqj_2cc}