Problem definition

As per official documentation, anonymous user is mentioned when making changes to auto-managed sprint:

If you configured an auto-managed sprint, when it auto-starts or auto-completes, you’ll get an email notification that Anonymous has made some changes to this sprint.

For specific needs in business processes, it would be beneficial if a specific user could be set to perform those changes, instead of Anonymous.

Suggested resolution

Implement the ability to change the user who performs changes on auto-managed Sprint.

We strongly place a request to change the attribution from "Anonymous" to "System" or a dedicated service user (e.g., "Jira Automation").

Technical Rationale: The current attribution is confusing because the action is not unauthenticated. The auto-managed sprint is executed by a background job that operates with full system authentication and has specific administrative permissions.

Audit Trail Integrity: The "Anonymous" label undermines the clarity of the audit log, forcing customers to differentiate between genuine unauthenticated public access and authenticated internal automation.

Misleading Semantics: The term "Anonymous" incorrectly implies a lack of permissions or identity, whereas the action is performed by a highly privileged, authenticated service context.

We believe this should be considered a necessary fix for data governance and compliance clarity, rather than a cosmetic enhancement.