Jitter is the measure of ticket activity while a ticket is in an Active status.
In this article
Which reports use Jitter?
See Jitter in Metrics overview, Retrospective, and Check-in.
See Jitter for individual tickets in Sprint movement and Ticket log.
What does Jitter measure?
Jitter indicates the amount of activity that occurred on a ticket while it was being actively worked on.
A high Jitter could mean a ticket's requirements are unclear and require additional communication between teams. It could also mean a ticket had multiple development and review cycles. A low Jitter could mean low collaboration between team members. You can think of this as a Goldilocks number: you don't want it to be too high or too low.
Identify a good range of Jitter for your team and keep an eye on it to help identify outliers and breaks in trends to ensure collaboration continues and roadblocks are removed.
How is Jitter calculated?
Jitter is calculated on a per-ticket basis. Total Jitter represents the sum of all ticket Jitter.
Ticket events include comments, ticket body modifications, and assignee changes.
First, Flow calculates the Jitter for an individual Jitter event on a ticket:
Jitter for a specific event type in a ticket = Number of times that Jitter event
occurred * (Weight of that Jitter event / Sum of all Jitter event weights in
the ticket project) * 100
Then, Flow adds together the Jitter from each event type on the ticket to find that ticket's Jitter:
Jitter for a ticket = Sum of Jitter for a Jitter event type in a ticket
Finally, Flow calculates total Jitter of tickets in a filter by adding together the Jitter on all tickets with Jitter in that filter:
Total Jitter of tickets in a filter = Sum of Jitter for all tickets in that filter
Tip: Adjust your Jitter event weights in your ticket project configurations to define which events you think are most impactful for your team. Also use this to remove events that your organization does not find important.
What data is included in Jitter?
Tickets accrue Jitter when:
- They're mapped to an Active status and get activity
- They're mapped to an Active status with a sub-state of Waiting and gets activity
Tickets don't accrue Jitter when:
- They're not mapped to an Active status
- They're mapped to a Not started or Done status or are in an unassigned status
Tickets are included in Jitter if:
- They are moved to their final Done status during the selected time period
- The selected user or a member of the selected team was an assignee on the ticket at any point once it moved into an Active status
Tickets aren't included in Jitter if:
- They haven't been moved to a Done status
- They are in a Canceled status
- The selected user or a member of the selected team has never been an assignee on the ticket or was only an assignee before the ticket moved into an Active status
- They have never had an assignee
- Their issue type has been excluded as part of ticket type assignment in ticket project configuration
Note: Since Jitter accrues when tickets haven't moved to a Done status, view Jitter for tickets not yet in a Done status as well as those in a Canceled status in Ticket log.