Skip to main content

Standard Epic Template

This guideline describes the custom standard fields used in the Epic template. For a more general picture of the standard work item template change process in Azure DevOps, see the ADO standard work item template change management process.

Overview​

The Epic template is an ABB customized template displaying the minimum requirements of fields including standard state as in the Azure DevOps Agile template plus ABB specific fields. These specific fields are described below.

The Configuration Management process team is responsible for updating the standard bug template that is found in Opex - Repos - Configuration Management. Both templates used on-premises and in the cloud are available.

List of standard custom fields to add:

Definition of Ready / Definition of Done​

Definition of Ready and Definition of Done are implemented as a custom control using the Appgami checklist extension.

Prerequisite: The Appgami checklist extension is needed and it requires a commercial license for each organization. If the extension is not available, work item type definitions cannot be loaded correctly. If the license expires, data will still be available in work items, and queries will still work, but checklists will not be visualized by the custom control.

DoR is made of 3 fields:

  • Definition of Ready
  • DoR Progress
  • DOR Completion

DoR

DoD is made of 3 fields:

  • Definition of Done
  • DoD Progress
  • DOD Completion

DoR

Example:

How to find work items where the Definition of Ready is not complete?
DoR Completion <> Yes

Security Relevant​

Security Relevant is a string field with a picklist (empty by default/True/False)

Is it likely that work will affect a security-critical component?

See How-to Work with Epics

DoR

Owner: Configuration Management Team