User Account Change Timeline(2.2.9)

User account changes are among the most compliance-sensitive Jira events. Every account added can reach data, and removing an account ends that account's access. This visual tracks when accounts are created, modified, and deleted over time.

What you can conclude

• Deletions of people's accounts outside known offboarding windows are the events a GDPR or NIS2 reviewer is most likely to ask about.
• For a creation spike in people's accounts with no corresponding onboarding event, a reviewer could ask who approved the new accounts.
• A steady, predictable pattern aligned with HR cycles means account changes follow joiners and leavers.
• App and customer accounts are not joiners and leavers: Jira marks an app account as belonging to an app or integration, including built-in ones such as Automation for Jira, and a customer account as belonging to a service-desk customer, for example someone who signed up on your portal or was added as a customer.
• The user events Jira sends name the account they are about, not who made the change, so who approved a change has to come from your identity provider or HR records.

How this chart works

Bar chart of the net change in user accounts per ISO week (creations minus deletions), with a line for all account activity (creations, updates, and deletions) on its own axis. Every count is also recorded by the type of account the event is about: person, app, customer, unknown (Jira did not return a type) or erased; the types add up to the count, and unknown and erased accounts are never counted as people. Follows the page date filter in whole weeks: a week is included when it falls entirely inside the selected range, the week in progress is included when the range reaches it, and a caption under the chart names a week that is left out. Cross-reference changes to people's accounts with HR records to validate that they were authorized.

The week in progress is shown at its value so far. Because the week is not yet complete, it covers only the events recorded so far and can move in either direction as the week closes.

A week in which Jira recorded events for the site but no account changes is shown as zero. A week in which no events at all were recorded for the site is left blank: it cannot be told apart from a gap in data collection, so it is not reported as zero.