Transition Events(2.1.12)

All the other visuals in this report aggregate and summarize — this one goes the other direction. When something looks unusual in the charts above, this table lets you drill down to the raw events behind it. You can see exactly which ticket changed, which field changed and its old and new value, who triggered the change, and when.

This is the audit log at the heart of the Workflow Transitions module. It is the starting point for any investigation that begins with "let me check what actually happened."

What you can conclude

• Use this table to verify specific patterns spotted in the charts above — for example, who is responsible for the backward transitions shown in the matrix.
• Filter by a specific actor to review their complete change history for the selected period.
• Filter by a specific ticket to see its full journey through the workflow from start to present.

How this chart works

Detailed event log with one row per changed field on an issue update: a status change is one row, and so is a change to the description, resolution, priority, summary or any other field Jira records. Columns: date, issue, summary, field, from, to, actor and project. Each row's actor is labeled with its type as Jira reports it: person, app, customer, unknown when Jira returned no type, erased, or system when no actor was recorded. The table shows the most recent 1,000 changes for the selected filters.

Use the date, project, and actor filters to narrow the view. The table is sortable by any column and works best as a drill-down companion to the other visuals in this report.