Bugs, issues, and risks in Azure Boards
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
The following fields track information about bugs, issues, and risks. These work item types are defined within the process template for the CMMI process.
Bug tracking fields
These fields are neither reported nor indexed.
| Field name | Description | Data type |
|---|---|---|
| Symptom | The unexpected behavior. Reference name=Microsoft.VSTS.CMMI.Symptom |
HTML |
| Proposed Fix | The proposed change to fix the reported problem. Reference name=Microsoft.VSTS.CMMI.ProposedFix |
HTML |
| Found in Environment | The software setup and configuration where the bug was found. Reference name=Microsoft.VSTS.CMMI.FoundInEnvironment |
String |
| Root Cause | The cause of the error. You can specify one of the following values: <br /- Coding Error - Design Error - Specification Error - Communication Error - Unknown To change the menu selection, see Customize a picklist. Reference name=Microsoft.VSTS.CMMI.RootCause |
String |
| How Found | How the bug was found. For example, a bug might have been found during a customer review or through ad hoc testing. Reference name=Microsoft.VSTS.CMMI.HowFound |
String |
Issue tracking fields
These fields are neither reported nor indexed.
| Field name | Description | Data type |
|---|---|---|
| Analysis | The root cause of the issue and one or more solutions that might resolve it. Reference name=Microsoft.VSTS.CMMI.Analysis |
HTML |
| Corrective Action Actual Resolution | What the team actually did to correct the issue. Reference name=Microsoft.VSTS.CMMI.CorrectiveActionActualResolution |
HTML |
| Corrective Action Plan | The proposed corrective action on which the team has agreed. Reference name=Microsoft.VSTS.CMMI.CorrectiveActionPlan |
HTML |
| Target Resolve Date | The date when the issue becomes critical and starts to affect the critical path of the project plan. Reference name=Microsoft.VSTS.CMMI.TargetResolveDate |
DateTime |
Risk tracking fields
These fields are neither reported nor indexed.
| Field name | Description | Data type |
|---|---|---|
| Contingency Plan | 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. Reference name=Microsoft.VSTS.CMMI.ContingencyPlan |
HTML |
| Mitigation Plan | 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. Reference name=Microsoft.VSTS.CMMI.MitigationPlan |
HTML |
| Mitigation Triggers | 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. Reference name=Microsoft.VSTS.CMMI.MitigationTriggers |
HTML |
| Probability | A number that 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. Reference name=Microsoft.VSTS.CMMI.Probability |
Integer |
Related articles
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for