Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
separatorbrackets
printablefalse

Overview

The Common Datsets section provides users with access to essential data sources that are frequently used to construct meaningful metrics and charts. These data sources are configured in the Configure Data Source/ Data sources tab.

Available Common Data Sources

  • Task Tracking System

    • Jira

    • Rally

    • Azure DevOps Board

  • Version Control

    • Azure Repos GIT

    • BitBucket

    • BitBucket Server (Stash)

    • GitHub

    • GitLab

...

Data Source type

Dataset

Task Tracking System

Ticket

TicketHistory

Worklog

Sprints

Releases

Version Control

Branch

Commit

PullRequest

PullRequestActions

Tag

Azure Board (TFS/VSTS) has fields with names that differ between Custom Metrics and for metric development, Perf names should be used:

  • State - Perf: Status

  • Area - Perf: Components

  • Iteration - Perf: Sprints

  • Tag - Perf: Labels

...

Info

To build a custom metric with using historical data you can use not only TicketHistory table but also a function ticket_snapshots.

Ticket_snapshots

A snapshot is a representation of tickets within a defined time interval, allowing for a quick view of the most recent ticket activity over specific periods. Ticket_snapshots is presented in the “Project Settings” section of the PerfQL Selection step.

...

  1. Custom burnup chart (without forecast)

Join Task Tracking datasets between each other

By default, Custom Metric v2 is created based on one table at a time. By using joins, you can retrieve data from two or more tables based on logical relationships between the tables and create a chart based on them.

...

Table

Condition

Ticket JOIN with

TicketHistory

Ticket.id=TicketHistory.workitem_id

Worklog

Ticket.id=Worklog.workitem_id

Sprint

Sprint.id=any(Ticket.sprints)

Release

Release.id=any(Ticket.fix_releases)

TicketHistory JOIN with

Ticket

TicketHistory.workitem_id=Ticket.id

Worklog

TicketHistory.workitem_id=Worklog.workitem_id

Sprint

Based on situation

Release

Based on situation

Worklog JOIN with

Ticket

Worklog.workitem_id=Ticket.id

TicketHistory

Worklog.workitem_id=TicketHistory.workitem_id

Sprint

Based on situation

Release

Based on situation

Sprint JOIN with

Ticket

Sprint.id=any(Ticket.sprints)

TicketHistory

Based on situation

Worklog

Based on situation

Mapping Azure DevOps Board with Ticket table

This mapping allows you to effectively use Azure DevOps Board data within the Ticket table for metric development and analysis.

...