Azure Boards | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013
You use planning, ranking, and priority fields to specify which work the team should complete first. By ranking and prioritizing work items, all team members gain an understanding of the relative importance of the work that they must accomplish.
Indicates whether or not the requirement is committed in the project. You can specify Yes or No.
Reference name=Microsoft.VSTS.CMMI.Committed, Data type=String
Indicates whether or not the issue is affecting the critical path of the project plan. You can specify Yes or No.
Reference name=Microsoft.VSTS.CMMI.Escalate, Data type=String
A subjective rating of the bug, issue, task, or test case as it relates to the business. You can specify the following values:
1: Product cannot ship without the successful resolution of the work item, and it should be addressed as soon as possible.
2: Product cannot ship without the successful resolution of the work item, but it does not need to be addressed immediately.
3: Resolution of the work item is optional based on resources, time, and risk.
Reference name=Microsoft.VSTS.Common.Priority, Data type=Integer
Bug, Change Request, Epic, Feature, Impediment, Issue, Product backlog item, Requirement, Risk, Shared Step, Task, Test Case, User Story
A subjective rating of the relative uncertainty around the successful completion of a user story.
Defined allowed values are:
1 - High
2 - Medium
3 - Low
Reference name=Microsoft.VSTS.Common.Risk, Data type=String
Epic, Feature, User Story (Agile)
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
Reference name=Microsoft.VSTS.Common.Severity, Data type=String
Bug, Issue (CMMI), Risk (CMMI)
Stack Rank 2
A number, usually assigned by a background process, used to track the list order of items on a backlog or board in the web portal.
Reference name=Microsoft.VSTS.Common.StackRank, Data type=Double
Bug, Epic, Feature, Requirement (CMMI), Risk (CMMI), Task, User Story (Agile)
A subjective unit of measure that captures the how the business value decreases over time. Higher values indicate that the epic or feature is inherently more time critical than those items with lower values.
Reference name=Microsoft.VSTS.Common.TimeCriticality, Data type=Double
Indicates the type of triage decision that is pending for the work item. You use this field when the work item is in the Proposed state.
You can specify one of the following values:
Reference name=Microsoft.VSTS.Common.Triage, Data type=String
The sequence of items on a product backlog page is determined according to where you have added or dragged the items. As you drag items, a background process updates either the Backlog Priority (Scrum) or Stack Rank (Agile, Basic, CMMI) field. These fields determine the order in which backlog items appear on a backlog page. They are assigned to type="Order" in the ProcessConfiguration file.