Jira Cloud user deactivation: license savings versus preserved issue history

On a low-traffic Jira Cloud instance, per-user licensing is the dominant recurring cost, and deactivating inactive accounts is the primary documented lever for releasing seats back to the subscription tier.

The transition is not equivalent to removal, and that is where the tradeoff sits. A deactivated user stops consuming a license, but Jira keeps the account's references in issue history, comments, work logs, and audit records, and it does not reassign or purge them automatically. Full deletion is destructive and normally requires reassigning the user's issues first, which is impractical for long-lived projects with sparse activity. There is no native 'archive user' state that both frees the seat and hides historical presence, so the choice is between cost and traceability. On Jira Data Center and Server, licensing is commonly tied to user tiers or capacity rather than active seats, so the same change may not reduce spend there.

What documented behavior should be confirmed for deactivated users in JQL filters, automation rules, and dashboards that reference them by name? Which criteria should separate accounts that are safe to deactivate from those that genuinely require deletion? And when the subscription tier is adjusted, how do deactivated users count toward the licensed total?