{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":16736,"path":"governance-risk-compliance/create-new-issue-opres-ws.md","title":"Create Issue form","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create Issue form\n\nUse the Create Issue form in Operational Resilience Workspace to add an issue to a business service or a scenario analysis.\n\n## Create Issue form\n\nFor a description of the field values, see the following table.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nIssue\n\n
\n\nNumber\n\n\n\nNumber of the issue. This field is auto-filled.\n\n
\n\nName\n\n\n\nName of the issue.\n\n
\n\nIssue source\n\n\n\nSource of the issue, such as Business service or Scenario analysis. This field is auto-filled.\n\n
\n\nIssue type\n\n\n\nSource 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\n- Control operative effectiveness failure\n- Control does not meet requirement\n- Control does not exist\n- Non-compliance to a regulation\n- Non-compliance to a policy\n- Improvement or suggestion to an existing policy\n- Recommendation for a new policy\n- process optimization or improvement\n- Observation\n- Data breach\n- Fraud\n- Misstatement\n- Training\n- Documentation\n\n
\n\nClassification\n\n\n\nClassification of the issue. This field is auto-populated with one of the following options:- Audit\n- Compliance\n- Operational Resilience\n- Risk\n- Vendor\n\n
\n\nLocation\n\n\n\nLocation of the issue.\n\n
\n\nState\n\n\n\nState of the issue. Available options are:- New\n- Analyze\n- Respond\n- Review\n- Closed Complete\n- Closed Incomplete\n\n
\n\nSubstate\n\n\n\nSubstate of the issue. This field is auto-filled.\n\n
\n\nPriority\n\n\n\nPriority of the issue. Available options are:- Critical\n- High\n- Moderate\n- Low\n- Planning\n\n
\n\nIssue rating\n\n\n\nRating of the issue. Available options are:- Very High\n- High\n- Moderate\n- Low\n- Very Low\n\n
\n\nDescription\n\n\n\nApprover of the scenario analysis plan.\n\n
\n\nAssignment\n\n
\n\nAssignment group\n\n\n\nAssignment group for the issue. For example, Application Development group.\n\n
\n\nAssigned to\n\n\n\nUser that the issue is assigned to.\n\n
\n\nIssue manager group\n\n\n\nManager group that the issue is assigned to. Available options are:- Compliance Managers\n- IT Risk Managers\n- Risk Managers\n\n
\n\nIssue manager\n\n\n\nManager that the issue is assigned to.\n\n
\n\nWatchlist\n\n\n\nUsers who are on the watchlist for the issue.\n\n
\n\nSchedule\n\n
\n\nDue date\n\n\n\nDate when the issue is due.\n\n
\n\nConfirmed date\n\n\n\nConfirmation date for the issue. This field is auto-filled.\n\n
\n\nPlanned start date\n\n\n\nPlanned start date for the issue.\n\n
\n\nPlanned end date\n\n\n\nPlanned end date for the issue.\n\n
\n\nDuration\n\n\n\nDuration for the issue in days, hours, minutes, and seconds.\n\n
\n\nCreated\n\n\n\nDate on which the issue is created. This field is auto-filled.\n\n
\n\nClosed\n\n\n\nDate on which the issue is closed.\n\n
\n\nActual start date\n\n\n\nActual start date for the issue.\n\n
\n\nActual end date\n\n\n\nActual end date for the issue.\n\n
\n\nActual duration\n\n\n\nActual duration for the issue in days, hours, minutes, and seconds.\n\n
\n\nIssue grouping\n\n
\n\nParent issue\n\n\n\nParent issue that is associated with the issue.\n\n
\n\nIssue group rule\n\n\n\nGroup rule for the issue. This field is auto-filled.\n\n
\n\nAction plan\n\n
\n\nRecommendation\n\n\n\nRecommendation for the issue.\n\n
\n\nAction plan\n\n\n\nAction plan for the issue.\n\n
\n\nActivity\n\n
\n\nWork notes\n\n\n\nWork notes for the issue.\n\n
\n\nAdditional comments\n\n\n\nAdditional comments for the issue.\n\n
\n\nSettings\n\n
\n\nFunctional domain\n\n\n\nFunctional domain that the issue belongs to. For example, an issue may belong to the IT Risk and Compliance domain.\n\n
"}}