{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":22779,"path":"intelligent-experiences/ai-control-tower/create-a-new-ai-issue-form.md","title":"Create new AI issue form","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create new AI issue form\n\nUse the Create New Issue form to identify and manage issues related to the impacted areas for the reported AI case.\n\nSee the following table for a description of the field values.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nNumber\n\n\n\nNumber of the issue. This field is automatically set to a request number.\n\n
\n\nName\n\n\n\nName of the issue. For example, `Cyber Attack on Acme`.\n\n
\n\nIssue source\n\n\n\nSource from where the issue was created. This field is automatically set to **AI case**.\n\n
\n\nIssue type\n\n\n\nType 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.\n- **Control operative effectiveness failure**: The control was well-designed but failed during execution or wasn't followed correctly.\n- **Control doesn’t meet requirement**: The control is in place but doesn't satisfy regulatory, policy, or business requirements.\n- **Control doesn’t exist**: There is no control present to address a known risk or requirement.\n- **Non-compliance to a regulation**: A law or regulation was not followed, potentially exposing the organization to penalties.\n- **Non-compliance to a policy**: An internal policy was not adhered to, which could lead to risks or inefficiencies.\n- **Improvement or suggestion to an existing policy**: A recommendation to enhance an existing policy for better clarity, coverage, or effectiveness.\n- **Recommendation for a new policy**: A proposal to create a new policy to address a gap or need that currently isn’t covered.\n- **Process optimization or improvement**: Opportunities identified to improve efficiency, accuracy, or effectiveness of a business process.\n- **Observation**: A general note or finding that may not be an issue now but could warrant attention.\n- **Data breach**: Unauthorized access, disclosure, or loss of sensitive or personal data.\n- **Fraud**: Intentional deception for personal or organizational gain, such as misappropriation of assets.\n- **Misstatement**: Errors or omissions in financial or operational reporting that misrepresent facts.\n- **Training**: Gaps or needs identified in knowledge or skills that require attention.\n- **Documentation**: Issues related to missing, outdated, or inaccurate documentation.\n- **Risk issue**: A broad risk-related concern that may not fall under other specific categories.\n- **Other**: Any issue that doesn't fit into the above types but is still worth tracking and resolving.\n\n
\n\nClassification\n\n\n\nClassification of the issue. The options are as follows:- **Compliance**\n- **Risk**\n- **Audit**\n- **Vendor Risk**\n\n
\n\nLocation\n\n\n\nLocation where the issue occurred. For example, Japan.\n\n
\n\nState\n\n\n\nWorkflow state of the issue. This field is automatically set to **Review**. The options are as follows:- **New**\n- **Analyze**\n- **Respond**\n- **Review**\n- **Closed Complete**\n- **Closed Incomplete**\n\n For more information on Issue management workflow and life cycle, see [View AI assets by life-cycle stage](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/intelligent-experiences/ai-control-tower/view-ai-assets-lifecycle-stage.md).\n\n
\n\nSubstate\n\n\n\nSubstate of the issue. This field is auto-filled.\n\n
\n\nPriority\n\n\n\nUrgency of the issue. It enables the team to triage requests effectively and respond based on how critical the request is. This field is automatically set to **Review**. The options are as follows:- **Critical**\n- **High**\n- **Moderate**\n- **Low**\n- **Planning**\n\n
\n\nIssue rating\n\n\n\nRating of the issue. The options are as follows:- **Very High**\n- **High**\n- **Moderate**\n- **Low**\n- **Very Low**\n\n
\n\nDescription\n\n\n\nDescription about the issue in detail. For example, ACME experienced a cyber attack that resulted in unauthorized access to internal systems.\n\n
\n\nAssignment\n\n
\n\nAssignment group\n\n\n\nGroup to whom the issue is assigned. For example, Risk Managers.\n\n
\n\nAssigned to\n\n\n\nUser to whom the issue is assigned.\n\n
\n\nIssue manager group\n\n\n\nManager group that the issue is assigned to. The options are as follows:- **Compliance Managers**\n- **IT Risk Managers**\n- **Risk Managers**\n\n
\n\nIssue manager\n\n\n\nManager to whom the issue is assigned.\n\n
\n\nWatch list\n\n\n\nPerson who must be informed about 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\nCreated\n\n\n\nDate on which the issue is created. This field is automatically set to the current date and time.\n\n
\n\nClosed\n\n\n\nDate on which the issue is closed.\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\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\nIssue group rule\n\n\n\nGroup rule for the issue. This field is auto-filled.\n\n
\n\nParent issue\n\n\n\nParent issue that is associated with the issue.\n\n
\n\nAction plan\n\n
\n\nRecommendation\n\n\n\nRecommendation for the issue. For example, `Enhance cybersecurity measures and provide regular security training`.\n\n
\n\nAction plan\n\n\n\nAction plan for the issue. For example, `Upgrade the firewall to the latest version and implement multi-factor authentication for all administrative accounts`.\n\n
\n\nActivity\n\n
\n\nWork notes \\(Private\\)\n\n\n\nNotes or information about the issue.\n\n
\n\nAdditional comments \\(Customer visible\\)\n\n\n\nAdditional information about the issue that you want to share with your customers.\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 AI Risk and Compliance domain.\n\n
"}}