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 - 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 Classification Classification of the issue. This field is auto-populated with one of the following options:- Audit - Compliance - Operational Resilience - Risk - Vendor Location Location of the issue. State State of the issue. Available options are:- New - Analyze - Respond - Review - Closed Complete - Closed Incomplete Substate Substate of the issue. This field is auto-filled. Priority Priority of the issue. Available options are:- Critical - High - Moderate - Low - Planning Issue rating Rating of the issue. Available options are:- Very High - High - Moderate - Low - Very Low 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 - IT Risk Managers - Risk 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.