Reporter Field Changes Over Time(5.3.5)

The reporter field identifies who raised an issue. In normal workflows, it almost never changes after creation. When it does change, it may indicate someone is retroactively reassigning accountability — altering the record of who was responsible for identifying a problem. This visual tracks how often reporter field changes occur so you can see whether this pattern is isolated or growing.

What you can conclude

• Any significant volume of reporter changes is unusual and warrants investigation — there are very few legitimate reasons to change who reported an issue.
• A spike in reporter changes in a specific week may correlate with a compliance review, an incident investigation, or a bulk edit; who made the changes is in the events, why is not.
• Zero reporter changes across all periods is the expected state — any deviation deserves scrutiny.

How this chart works

Weekly line chart showing the count of reporter field changes alongside total event volume for context. Reporter changes are counted by the type of account Jira reports for whoever made them (person, app, customer, unknown when Jira returned no type, erased, or system when no actor was recorded); people's changes form the headline and the others are counted beside them, never inside them. Use the date and project filters to focus on specific teams or periods.

The week in progress is shown at its count so far. Because the week is not yet complete, it covers only what has been recorded up to now and can only grow as the week closes.