Create Issue form
Use the Create Issue form in Compliance Workspace to create an issue or add an existing issue to a regulatory task.
Create Issue form
For a description of the field values, see the following table.
|
Field |
Description |
|---|---|
|
Issue | |
|
Number |
Number of the issue. This field is auto-filled. |
|
Name |
Name of the issue. For example, |
|
Issue source |
Source from where the issue was created, such as risk event or risk assessment. This field is auto-filled. |
|
Issue type |
Type of the issue. The options are as follows:- Control design effectiveness failure: The control was poorly designed and cannot effectively prevent or detect the intended risk.
|
|
Classification |
Classification of the issue. The options are as follows:- Audit
|
|
Location |
Location where the issue occurred. For example, United States. |
|
State |
Lifecycle stage of the issue. The options are as follows:- New
|
|
Substate |
Substate of the issue. This field is auto-filled. |
|
Priority |
Urgency of the issue. The options are as follows:- 1-Critical
|
|
Issue rating |
Severity or risk level of the issue. The options are as follows:- 1-Very High
|
|
Description |
Detailed explanation of the issue. For example, |
|
Assignment | |
|
Assignment group |
Group to whom the issue is assigned. For example, GRC Business Users. |
|
Assigned to |
User to whom the issue is assigned. |
|
Issue manager group |
Manager group responsible for overseeing the issue. Available options are:- Compliance Managers
|
|
Issue manager |
Manager responsible for overseeing the issue. |
|
Watchlist |
Users who must receive notifications about updates to the issue. |
|
Schedule | |
|
Due date |
Date when the issue is due. |
|
Confirmed date |
Confirmation date for the issue. This field is auto-filled. |
|
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 auto-filled. |
|
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 that is associated with the issue. |
|
Issue group rule |
Group rule for the issue. This field is auto-filled. |
|
Action plan | |
|
Recommendation |
Recommendation for the issue. For example, |
|
Action plan |
Action plan for the issue. For example, |
|
Activity | |
|
Work notes |
Internal notes about the issue. These are private and visible only to users with access to the issue record. |
|
Additional comments |
Additional information about the issue that you want to share with your customers. These are visible to external stakeholders and customers. |
|
Settings | |
|
Functional domain |
Functional domain that the issue belongs to. For example, IT risk and compliance. |
--- title: Create Issue form description: Use the Create Issue form in Compliance Workspace to create an issue or add an existing issue to a regulatory task. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/regulatory-change-management-service-portal/create-new-issue-reg-change-comp-ws.html release: australia product: Regulatory Change Management Service Portal classification: regulatory-change-management-service-portal topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 3 breadcrumb: [Create or add an issue related to a regulatory task, Manage regulatory tasks, Regulatory Change Management, Governance, Risk, and Compliance] --- # Create Issue form Use the Create Issue form in Compliance Workspace to create an issue or add an existing issue to a regulatory task. ## Create Issue form 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 auto-filled. </td></tr><tr><td> Name </td><td> Name of the issue. For example, `Non-compliant control`. </td></tr><tr><td> Issue source </td><td> Source from where the issue was created, such as risk event or risk assessment. This field is auto-filled. </td></tr><tr><td> Issue type </td><td> Type of the issue. The options are as follows:- **Control design effectiveness failure**: The control was poorly designed and cannot effectively prevent or detect the intended risk. - **Control operative effectiveness failure**: The control was well-designed but failed during execution or wasn't followed correctly. - **Control doesn’t meet requirement**: The control is in place but doesn't satisfy regulatory, policy, or business requirements. - **Control doesn’t exist**: There is no control present to address a known risk or requirement. - **Non-compliance to a regulation**: A law or regulation was not followed, potentially exposing the organization to penalties. - **Non-compliance to a policy**: An internal policy was not adhered to, which could lead to risks or inefficiencies. - **Improvement or suggestion to an existing policy**: A recommendation to enhance an existing policy for better clarity, coverage, or effectiveness. - **Recommendation for a new policy**: A proposal to create a policy to address a gap that currently isn’t covered. - **Process optimization or improvement**: Opportunities identified to improve efficiency, accuracy, or effectiveness of a business process. - **Observation**: A general note or finding that may not be an issue now but could warrant attention. - **Data breach**: Unauthorized access, disclosure, or loss of sensitive or personal data. - **Fraud**: Intentional deception for personal or organizational gain, such as misappropriation of assets. - **Misstatement**: Errors or omissions in financial or operational reporting that misrepresent facts. - **Training**: Gaps or needs identified in knowledge or skills that require attention. - **Documentation**: Issues related to missing, outdated, or inaccurate documentation. - **Risk issue**: A broad risk-related concern that may not fall under other specific categories. - **Other**: Any issue that doesn't fit into the above types but is still worth tracking and resolving. </td></tr><tr><td> Classification </td><td> Classification of the issue. The options are as follows:- **Audit** - **Compliance** - **Risk** - **Vendor risk** </td></tr><tr><td> Location </td><td> Location where the issue occurred. For example, United States. </td></tr><tr><td> State </td><td> Lifecycle stage of the issue. The options are as follows:- **New** - **Analyze** - **Respond** - **Review** - **Closed Complete** - **Closed Incomplete** </td></tr><tr><td> Substate </td><td> Substate of the issue. This field is auto-filled. </td></tr><tr><td> Priority </td><td> Urgency of the issue. The options are as follows:- **1-Critical** - **2-High** - **3-Moderate** - **4-Low** - **5-Planning** </td></tr><tr><td> Issue rating </td><td> Severity or risk level of the issue. The options are as follows:- **1-Very High** - **2-High** - **3-Moderate** - **4-Low** - **5-Very Low** </td></tr><tr><td> Description </td><td> Detailed explanation of the issue. For example, `The "Manage change requests" control does not meet compliance requirements.` </td></tr><tr><td class="sub-head" colspan="2"> Assignment </td></tr><tr><td> Assignment group </td><td> Group to whom the issue is assigned. For example, GRC Business Users. </td></tr><tr><td> Assigned to </td><td> User to whom the issue is assigned. </td></tr><tr><td> Issue manager group </td><td> Manager group responsible for overseeing the issue. Available options are:- **Compliance Managers** - **IT Risk Managers** - **Risk Managers** </td></tr><tr><td> Issue manager </td><td> Manager responsible for overseeing the issue. </td></tr><tr><td> Watchlist </td><td> Users who must receive notifications about updates to 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 auto-filled. </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 auto-filled. </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 that is associated with the issue. </td></tr><tr><td> Issue group rule </td><td> Group rule for the issue. This field is auto-filled. </td></tr><tr><td class="sub-head" colspan="2"> Action plan </td></tr><tr><td> Recommendation </td><td> Recommendation for the issue. For example, `Ensure that changes to the entity's controls follow an approved change process.` </td></tr><tr><td> Action plan </td><td> Action plan for the issue. For example, `Leverage the approved change management procedures in the RCM.` </td></tr><tr><td class="sub-head" colspan="2"> Activity </td></tr><tr><td> Work notes </td><td> Internal notes about the issue. These are private and visible only to users with access to the issue record. </td></tr><tr><td> Additional comments </td><td> Additional information about the issue that you want to share with your customers. These are visible to external stakeholders and customers. </td></tr><tr><td class="sub-head" colspan="2"> Settings </td></tr><tr><td> Functional domain </td><td> Functional domain that the issue belongs to. For example, IT risk and compliance. </td></tr></tbody> </table>
| title | Create Issue form |
| description | Use the Create Issue form in Compliance Workspace to create an issue or add an existing issue to a regulatory task. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/governance-risk-compliance/regulatory-change-management-service-portal/create-new-issue-reg-change-comp-ws.html |
| release | australia |
| product | Regulatory Change Management Service Portal |
| classification | regulatory-change-management-service-portal |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 3 |
| breadcrumb | Create or add an issue related to a regulatory taskManage regulatory tasksRegulatory Change ManagementGovernanceRiskand Compliance |