Issue Summary

When a user invokes a Rovo agent (either the built-in Rovo agent or a custom agent) and asks it to update a Jira issue field, such as story points the issue's change history records the update as if the user made it directly. There is no indication in the audit trail that a Rovo agent performed the action.

The expected behavior is that Rovo agents have their own distinct account/identity similar to how "Automation for Jira" operates as a dedicated system actor so that the history log shows:

"Rovo agent updated story points on behalf of [User]"

rather than:

"[User] updated story points"

This request is not about permissions. It is understood and accepted that the agent operates using the invoking user's permissions. The request is purely about attribution and traceability in the issue history and audit log.

Steps to Reproduce

1. Navigate to a Jira issue (e.g., a Story with story points set to a known value).
2. Open the Rovo agent panel (either the built-in Rovo agent or a custom agent configured on the project).
3. Ask the Rovo agent to update a field — e.g., "Update story points to 3".
4. The agent confirms and executes the update. Click Accept when prompted.
5. Refresh the issue page and verify the field has been updated.
6. Open the issue's History tab and examine the change log entry for the field update.

Expected Results

The issue history should show:

• Actor: Rovo Agent (or the specific custom agent name, e.g., "My Custom Agent")

• Attribution: "on behalf of [User Name]"

• Example entry: "Rovo Agent updated Story Points from 5 to 3 on behalf of [User]"

Actual Results

The issue history shows:

• Actor: The invoking user

• Entry: "[User] updated Story Points from 5 to 3"

There is no indication that a Rovo agent performed the change. The audit trail is indistinguishable from a manual user edit, making it impossible to determine whether a change was made by a human or an AI agent.

Additional Context

• Not a permissions issue. The agent uses the invoking user's permissions to execute actions. The request is solely about how the change is attributed in history and audit logs.

• Affects both built-in and custom agents. Even custom agents that have their own configured name and identity still attribute changes to the invoking user in the Jira history log.

• Agent Accounts (upcoming): The concept of "agent accounts" is acknowledged https://jira.atlassian.com/browse/AUTO-2337. The request is specifically that Rovo should have its own system-level ID by default, independent of custom agent configurations, so that all Rovo-initiated changes are identifiable as such in audit logs.
• Compliance and audit impact. For organizations with strict change-tracking or compliance requirements, the current behavior makes it impossible to distinguish agent-driven changes from manual user actions in audit reports, reports, and exports.

Workaround

There is currently no known workaround for this behavior. All changes made via Rovo agents will appear as the invoking user in the Jira issue history.