Ticket complexity allows you to understand the relative complexity of your tickets using 4 different possible Units of Measurement, all based on the commits linked to your tickets:

Unit of Measurement


Changed Files

The unique number of files where changes have been made in commits related to each ticket.

Changed Lines

Total inserted and deleted lines made in commits related to each ticket


Number of unique individuals active on the commits and pull requests related to each ticket


Number of unique repositories affected by commits related to each ticket

This metric includes all completed tickets within the selected time range that are linked to any commits. For more about how we look for links between Tickets and Commits, please see details in our Commits without a ticket reference metric.

Some examples

Complexity by Story Points

Below we look at the complexity of tickets based on the number of developers involved. When breaking down this complexity score (average developers) by Story Points we see a strong correlation between the story points value and complexity. This, in turn, highlights very effective estimation by this team, where their estimates are able to correctly predict the actual complexity of the work.

Changed Lines for different Issue Types

Using the Changed Lines unit of measurement and then breaking down the metric by Issue Type we can start to understand the relative complexity of different types of change. Below, when looking over time, we can see a fairly consistent complexity of the Feature issue type, compared to the more sporadic complexity of Technical Improvements.

Did this answer your question?