This documentation is archived and is not being maintained.

Fields that Track Bugs, Issues, and Risks (CMMI)

You use the fields described in this topic to track information that is specific to one of these types of work items: Bugs, Issues, and Risks. For more information, see Bug (CMMI), Issue (CMMI), and Risk (CMMI).

These fields are available only if your team project is based on the process template for Microsoft Solutions Framework (MSF) CMMI Process Improvement v5.0.

NoteNote

For information about data types and default field attributes, see Working with Work Item Fields.

In this topic

The fields that the following table describes are neither reported nor indexed.

Field name

Description

Reference name

Data type

Symptom

Describes the unexpected behavior.

Microsoft.VSTS.CMMI.Symptom

HTML

Proposed Fix

Describes the proposed change to fix the reported problem.

Microsoft.VSTS.CMMI.ProposedFix

HTML

Found in Environment

Describes the software setup and configuration where the bug was found.

Microsoft.VSTS.CMMI.FoundInEnvironment

String

Root Cause

Describes the cause of the error. You can specify one of the following values:

  • Coding Error

  • Design Error

  • Specification Error

  • Communication Error

  • Unknown

Microsoft.VSTS.CMMI.RootCause

String

How Found

Describes how the bug was found. For example, a bug might have been found during a customer review or through ad hoc testing.

Microsoft.VSTS.CMMI.HowFound

String

The fields that the following table describes are not indexed.

Field name

Description

Reference name

Data type

Default value of the reportable type attribute

Analysis

Describes the root cause of the issue and one or more solutions that might resolve it.

Microsoft.VSTS.CMMI.Analysis

HTML

None

Corrective Action Actual Resolution

Describes what the team actually did to correct the issue.

Microsoft.VSTS.CMMI.CorrectiveActionActualResolution

HTML

None

Corrective Action Plan

Describes the proposed corrective action on which the team has agreed.

Microsoft.VSTS.CMMI.CorrectiveActionPlan

HTML

None

Impact on project promise

Specifies a subjective rating of the impact of a bug on the project. You can specify the following values:

  • 1 - Critical

  • 2 - High

  • 3 - Medium

  • 4 - Low

    NoteNote
    The name of the field that appears in the query editor is Severity. You also use this field to track the severity for bugs and risks.

Microsoft.VSTS.Common.Severity

String

Dimension

Target Resolve Date

Specifies a date for when the issue becomes critical and starts to affect the critical path of the project plan.

Microsoft.VSTS.CMMI.TargetResolveDate

DateTime

None

The fields that the following table describes are neither reported nor indexed.

Field name

Description

Reference name

Data type

Contingency Plan

Describes the actions to take if the risk occurs.

You can create and link tasks to the Risk work item to track the work that the team must complete to implement the contingency plan. Also, you can create an Issue work item to track one or more issues on which the risk has an impact.

Microsoft.VSTS.CMMI.ContingencyPlan

HTML

Mitigation Plan

Describes the actions to take to reduce the probability or impact of the risk.

You can create and link tasks to the Risk work item to track the work that the team must complete to implement the mitigation plan.

Microsoft.VSTS.CMMI.MitigationPlan

HTML

Mitigation Triggers

Describes the conditions or events that determine how the team might mitigate a risk. For example, the triage team might authorize and obtain a reserve generator if the weather forecast is predicting an ice storm or hurricane to hit within 50 miles of the office within the next four days.

Microsoft.VSTS.CMMI.MitigationTriggers

HTML

Probability

Indicates the chance that the risk will occur. A valid probability number is between 1 and 99, where 99 indicates that the risk is almost certain to occur.

Microsoft.VSTS.CMMI.Probability

Integer

Show: