If you are trying to build a more detailed view of "What are we delivering?", this metric is likely to provide you with the answers you need. Whilst it appears quite simplistic on the surface, Completed tickets is actually a robust metric that enables you to build a number of different perspectives on your output through breakdowns and filters.
Let's take a look at some examples.
Sample Use Cases
Story Points Delivered by Team
How to configure this: using Completed Tickets,
Simply select Story Points in the Unit of Measurement calculation step
Add a breakdown by board to see your total velocity over time, broken down by team
Stories delivered by Sprint
How to configure this: using Completed Tickets Count, apply an Issue Type filter to only view Stories and then add a breakdown by Sprint so you can see the Stories delivered each sprint over time.
Tickets delivered by Benefit type (or whatever custom fields you use)
How to configure this: using Completed Tickets Count, apply an Issue Type filter to only view Stories and then choose the breakdown that captures whatever custom field you use in Jira to categorise Benefit. (note: whilst we have used 'benefit' here, this can be applied to any custom field that you use in Jira).
Stories delivered by Epic
How to configure this: using Completed Tickets Count, apply an Issue Type filter to only view Stories and then choose the Epic Link breakdown to see how many are delivered per Epic over time.
Setting up this metric is very simple. Once you have added the right metric to your dashboard, we recommend that you start by applying the filters first. From the Filters drop down, select the area you'd like to filter and then the values to filter (below we've shown an example of an Issue Type filter to show Stories only)
Next, choose how you'd like the data broken down in the UI. You can choose to view these breakdowns by any of the standard or custom fields from Jira that we've added for you (if you don't see a custom field, let us know and we'll add it for you). Below is an example of a breakdown by Board (i.e. team).