Risks, Issues, Change Requests, and Action Items › Issues › How to Create Issues › Close Risks and Track as Issues

Close Risks and Track as Issues

After reviewing risk assumptions or symptoms and determining the probability of the risk is high, close the risk and track it as an issue. The new issue inherits the risk name and description and some of its values, such as Status ("Open") and Date Created (current calendar date).

Creating an issue from a risk brings awareness, actions, and tasks around an issue for conclusion by the project team. Additionally, it allows the team to keep a record of issues and their outcome for analysis at project closure and future project planning.

You can also connect other risks or issues related to this issue. Connecting all related issues and risks help you trace dependencies and recognize trends in future analysis and audits.

The Originating Risk field displays on the issue properties. This field is a link to the risk from which the issue derived.

Follow these steps:

1. Open the project and click Risks/Issues/Changes.

   The risks page appears.

2. Click the risk name.

   The risk main page appears.

3. Complete the following field:

   Status

   Specifies the status of this risk.

   Values: Open, Work in Progress, Closed, or Resolved

   Default: Open

   Required: Yes

   Select "Closed".

4. Save the changes.
5. Click Create Issue.

   The create page appears.

6. Complete the following fields:

   Issue Name

   Defines the short name for the issue. If you create an issue from a closed risk, the value for this field is from the Risk Name field on the risk properties page.

   Limit: 64 characters

   Required: Yes

   Issue ID

   Defines the identifier for the issue.

   Required: Yes

   Description

   Defines the short description for the issue. If you create an issue from a closed risk, the value for the field is derived from the Description field on the risk properties page.

   Required: No

   Category

   Defines the issue category to assign this issue. If you create an issue from a closed risk, the value for the field is derived from the Category field on the risk properties page.

   Values: Objectives, Sponsorship, Funding, Resource Availability, Interdependencies, Technical, Human Interface, Organizational Culture, Supportability, Implementation, and Flexibility

   Owner

   Defines the name of the resource who is managing the risk. This resource is responsible for verifying that the issue is managed and tracked appropriately through its lifecycle. If you create an issue from a closed risk, the value for this field is from Owner field on the risk properties page.

   Default: The resource currently logged in

   Required: Yes

   Status

   Specifies the status of the issue.

   Values: Open, Work in Progress, Closed, or Resolved

   Default: Open

   Required: Yes

   Creator

   Displays the name of the resource who created the issue.

   Default: The resource currently logged in

   Updated by

   Displays the name of the resource who last updated the issue.

   Default: The resource currently logged in

7. Complete the following field in the Details section.

   Target Resolution Date

   Defines the date for resolving the issue. The date requires to be the same or earlier than the impact date.

   Default: Current date

8. Save the changes.

More information:

How to Create Issues

Create Issues