Create Issue form
Use the Create Issue form in Operational Resilience Workspace to add an issue to a business service or a scenario analysis.
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. |
|
Issue source |
Source of the issue, such as Business service or Scenario analysis. This field is auto-filled. |
|
Issue type |
Source from where the issue was created. This field is auto-populated with one of the following options based on how the issue is created:- Control design effectiveness failure
|
|
Classification |
Classification of the issue. This field is auto-populated with one of the following options:- Audit
|
|
Location |
Location of the issue. |
|
State |
State of the issue. Available options are:- New
|
|
Substate |
Substate of the issue. This field is auto-filled. |
|
Priority |
Priority of the issue. Available options are:- Critical
|
|
Issue rating |
Rating of the issue. Available options are:- Very High
|
|
Description |
Approver of the scenario analysis plan. |
|
Assignment | |
|
Assignment group |
Assignment group for the issue. For example, Application Development group. |
|
Assigned to |
User that the issue is assigned to. |
|
Issue manager group |
Manager group that the issue is assigned to. Available options are:- 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 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. |
|
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 that the issue belongs to. For example, an issue may belong to the IT Risk and Compliance domain. |
--- title: Create Issue form description: Use the Create Issue form in Operational Resilience Workspace to add an issue to a business service or a scenario analysis. locale: en-US canonical_url: https://www.servicenow.com/docs/r/governance-risk-compliance/create-new-issue-opres-ws.html release: brazil topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Creating or adding an issue, Manage, Operational Resilience, Governance, Risk, and Compliance] --- # Create Issue form Use the Create Issue form in Operational Resilience Workspace to add an issue to a business service or a scenario analysis. ## 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. </td></tr><tr><td> Issue source </td><td> Source of the issue, such as Business service or Scenario analysis. This field is auto-filled. </td></tr><tr><td> Issue type </td><td> Source from where the issue was created. This field is auto-populated with one of the following options based on how the issue is created:- Control design effectiveness failure - Control operative effectiveness failure - Control does not meet requirement - Control does not 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 auto-populated 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. Available options are:- 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> Priority of the issue. Available options are:- Critical - High - Moderate - Low - Planning </td></tr><tr><td> Issue rating </td><td> Rating of the issue. Available options are:- Very High - High - Moderate - Low - Very Low </td></tr><tr><td> Description </td><td> Approver of the scenario analysis plan. </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, Application Development group. </td></tr><tr><td> Assigned to </td><td> User that the issue is assigned to. </td></tr><tr><td> Issue manager group </td><td> Manager group that the issue is assigned to. Available options are:- 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 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. </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 that the issue belongs to. For example, an issue may belong to the IT Risk and Compliance domain. </td></tr></tbody> </table>
| title | Create Issue form |
| description | Use the Create Issue form in Operational Resilience Workspace to add an issue to a business service or a scenario analysis. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/governance-risk-compliance/create-new-issue-opres-ws.html |
| release | brazil |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | Creating or adding an issueManageOperational ResilienceGovernanceRiskand Compliance |