Adding an issue to a walkthrough, a test plan, a test, or a risk

Professional Managers and Professional Users can add issues to a walkthrough, test plan, test, or risk directly from its card in Assessments. Each card also includes the full list of issues that have been added by you or others in Assessments and Projects, which you can view or edit.

  1. Under My Activities, select the expand arrow to open a card.
  2. Select Add an Issue.
  3. Complete the fields in the Add Issue screen.

    Note

    Rich text fields cannot exceed 524,288 characters.

    Tip

    To enable spell check on rich text fields, do one of the following:

    • Chrome, Firefox, or Safari CTRL + right-click within the field on Windows or Command + right-click on Mac
    • Internet Explorer or Microsoft Edge open your browser settings and turn on spell check / highlighting of misspelled words

    FieldDescription

    Title/Headline

    optional

    the title of the issue

    The maximum length is 255 characters.

    Description

    a detailed description of the issue

    Owner

    specifies the person responsible for the issue

    • If you specify a user that has been added to the Diligent One instance, the person receives an email notifying them that they have been assigned the issue if the issue is published. If the issue is not published, the person receives this email when the issue is published.
      Note

      When you bulk upload issues and specify a Diligent One user's email in the Owner field, the person is also automatically assigned the issue in the Projects app. However, the person does not receive an email notification about the issue assignment.

    • If you specify a name or email of a person that has not been added to the Diligent One instance, the person's name or email displays in the field, but the person is not automatically assigned the issue and notified via email.
    Issue Type

    specifies the classification of the issue, such as "Deficiency", "Significant Deficiency", "Material Weakness", or "Management Recommendation"

    Date Identified

    specifies the date when the issue was identified

    Severity

    optional

    specifies the intensity of the issue, such as "High", "Medium", or "Low"

    Published

    optional

    specifies whether the issue is visible to all users (Published), or hidden from users assigned the Contributor Tester, Contributor User, Oversight Executive, and Oversight Reviewer roles (Not Published). Issues must be published before Diligent One notifies the owner.

    Issues must be published to appear in Strategy when risks are linked to objectives. For more information, see Defining risk treatment.

    Recommendation

    optional

    the recommended actions to be taken based on the issue

    Custom Issue attributes

    optional

    a maximum of 10 custom attribute fields associated with the issue

    Project Admins and Project Type Admins can define custom attributes for issues under Manage project types.

  4. Select Show more to add additional details to the issue.
    FieldDescription

    Issue ID

    optional

    the numeric, alphabetic, or alpha-numeric identifier for the issue

    The maximum length is 255 characters.

    Executive Owner

    optional

    specifies the executive owner of the issue

    • If you specify a user that has been added to the Diligent One instance, the person receives an email notifying them that they have been assigned the issue.
      Note

      When you bulk upload issues and specify a Diligent One user's email in the Executive Owner field, the person is also automatically assigned the issue in the Projects app. However, the person does not receive an email notification about the issue assignment.

    • If you specify a name or email of a person that has not been added to the Diligent One instance, the person's name or email displays in the field, but the person is not automatically assigned the issue and notified via email.

    Project Owner

    optional

    specifies the project owner of the issue

    • If you specify a user that has been added to the Diligent One instance, the person receives an email notifying them that they have been assigned the issue.
      Note

      When you bulk upload issues and specify a Diligent One user's email in the Project Owner field, the person is also automatically assigned the issue in the Projects app. However, the person does not receive an email notification about the issue assignment.

    • If you specify a name or email of a person that has not been added to the Diligent One instance, the person's name or email displays in the field, but the person is not automatically assigned the issue and notified via email.

    Risk / Impact

    optional

    the description of the risk or the impact the issue will have

    Scope

    optional

    the extent to which the issue affects the organization, such as "Local" or "Global"

    Escalation Level

    optional

    the person, department, or organizational body that this issue should be brought to, such as "Owner", "Executive", or "Board"

    Cause

    optional

    what caused the issue to occur

    Effect

    optional

    the effect the issue will have on the organization

    Executive Summary

    optional

    a high level overview of the issue that typically summarizes information from other related fields, such as risk/impact, cause, and effect

    Cost Impact

    optional

    the estimate or actual monetary cost associated with the issue

  5. Select Save to record your updates and add the issue.
  6. Select Issues to view the full list of issues that have been added for that walkthrough, test plan, test, or risk.
  7. Select the expand arrow for the Issues section to view the full list of issues that have been added for that walkthrough, test plan, test, or risk.
  8. Select the edit icon for an issue to update any of the fields listed above.
    Note

    Only Professional Managers and Professional Users are able to edit issues.

  9. Select any issue from the list to view it in the Projects application and access additional functions, including the Follow-up & Remediation and Retest Information sub tabs. See Remediation and retesting issues.
    To learn more about managing issues in Projects, see Managing issues and remediation.

Contextual information

When you expand a walkthrough, test plan, test, or risk card, you can view buttons at the bottom that provide you contextual information. You can view and manage information about the following:

  • Issues

  • Requests

  • Test Plans

  • Associated Risks

  • History

  • Control X-Ray

You can click the button for which you want to view or manage information. Click All to open all the contextual information buttons. On the information card, you can use the , , or icon to move, expand, or contract the card respectively.

For the description of buttons, see the Contextual information buttons table.

Contextual information buttons
Button Description
Issues

Displays the number of issues associated with the activity.

It displays for the following activity types:

  • Walkthrough (Controls)

  • Test (Controls)

  • Test plan (Controls)

  • Risks

Requests

Displays the number of requests associated with the activity.

It displays for the following activity types:

  • Walkthrough (Controls)

  • Test (Controls)

  • Test plan (Controls)

  • Risks

Test Plan

Displays the number of test plans associated with a test or a walkthrough.

The button doesn’t display when a test or a walkthrough is in one of the following states:

  • Completed

  • Preparer has signed off and is about to be assigned to the next reviewer after a non-preparer sign off.

Associated Risk

Displays the number of risks the selected Control helps to mitigate.

This button doesn’t display when a test, test plan, or walkthrough is completed.

History Displays when a Control is signed off by a preparer.
Control X-Ray

Displays for a test, test plan, and walkthrough. Displays information such as the results of previous testing and key attributes. You can use this information to gain a better understanding of the activities that you are working on in Assessments.

The following contextual information is available:

  • A link to the procedure or control

  • A link to the source framework, if applicable and its attributes

  • Previous testing results and sample sizes Related risks Previous issues - Issues do not appear if they were not published or were not created on the related procedure or control page. For more information, see Recording issues.

  • Related narratives

  • Related compliance maps

  • Related assets - If you have a subscription to IT Risk Management, have associated assets to a risk category in a project, and view a control associated with that risk category. For more information, see Working with assets

Associated Controls

Displays when you expand a risk card.

Displays the associated controls.

Attributes Displays the attributes of an action.