Team Re-routing After Intake(JIRA:1.5.11)
VisualAn issue that changes team soon after it is created did not stay with the first team it was routed to. This visual shows, for each project and request type, how many new issues were routed to a team and how many of them moved to a different team within 7 days of creation.
What you can conclude
- A request type with a high re-routing share sends many of its issues on to a second team in their first week; a reviewer could ask how issues of that type are routed at intake.
- Re-routing that concentrates in one request type of a project points at that type's routing rather than at the project as a whole.
- A share of 0% over many routed issues is a measured zero: none of them changed team in their first 7 days. A project or request type with no issue routed to a team does not appear at all.
How this chart works
Horizontal bars, one per project and request type, showing the share of issues routed to a team that were re-routed within 7 days of creation. The table below lists the counts behind each bar: issues routed to a team, re-routed issues, and re-routes, the number of team changes.
An issue counts as routed to a team when it holds a team at any point in its first 7 days, whether the team was set when it was created or later in that week. A re-route is a change from one team to a different team within 7 days of creation. Setting a team on an issue that had none is intake, not a re-route, and clearing the team is not a re-route either. Each change counts once, even when Jira records it on two events.
Issues are grouped by the project they were created in and by the latest request type recorded for them. Issues without a recorded request type, which includes every issue outside a service project, form one group, "No request type recorded".
The date range selects issues by the day they were created. The creation days still inside their first week are not counted: an issue created in the last 7 days can still be re-routed, so its day enters the shares and counts only once that week is complete.
Only issues whose creation MetaFrazo recorded together with the issue's field values are counted, because for any other issue the team it was created with is not known. On a site connected before MetaFrazo began recording field values, issues created before that date are not counted.