Rovo chat fails to create/update Jira work items: "Team id '{accountIdOrAri=...}' is not valid

Question

Summary: When using Rovo chat in Jira to create or edit a work item in a project that has the Team field, the action fails. Rovo passes the entire Team object instead of just the team ID string, so Jira rejects the request. This affects Rovo chat directly, not only custom agents. Error message: "Team id '{accountIdOrAri=stringValue[value=], error=nullValue[], user=mapValue[values={accountId=..., avatarUrl=..., name=, id=}], status=stringValue[value=ready]}' is not valid." Steps to reproduce: * Open a Jira work item (an Epic in my case) in a project that has the Team field. * Open Rovo chat with the work item as context. * Ask Rovo to create a work item (for example a Bug) or update a field. * Rovo prepares the request, but on execution the error above appears and nothing is created. Expected result: The work item is created or updated, with the Team field sent as a plain team ID string (or skipped when not needed). Actual result: The action fails because the full Team object (accountId, avatarUrl, name, status) is sent instead of the team ID string. Additional notes: * The same error appears in the Rovo chat panel and in a custom agent built in Studio, so the cause is in the shared Jira tool, not in any agent's instructions. * Adding instructions such as "pass only the team ID" does not help. Impact: Rovo cannot create or edit work items in projects that use the Team field, which blocks common workflows such as bug reporting. Has anyone found a workaround, or is this a known bug?"

Bhaargavi Natarajan · Answer

@Nikola Perisic Thanks for the welcome :) but you mentioned the incorrect person.

@Bhavini Kapadia is the reporter - pls check it out Bhavini!

Martin Runge · Answer

Hi @Bhavini Kapadia,

I would also try telling Rovo the team explicitly as a plain UUID or ARI string (for example "set Team to 8f2c...") instead of letting it inherit the team from the work item context, since the failure only appears when it copies the already resolved team object.

If that still breaks, I would check whether the project uses the platform Atlassian Team field or the older Advanced Roadmaps Team custom field, because they expect different values, and removing the field from the create screen under Project settings > Screens is a cleaner block than making it optional in the field configuration.

Servus (that is hello and goodbye where I live), Martin

Nikola Perisic · Answer

Welcome @Bhaargavi Natarajan

This is a known bug stemming from how Rovo's underlying Jira integration skill deserializes the Atlassian Team entity vs. how the Jira REST API expects field inputs.

When Rovo pulls context from an existing ticket, it retrieves the Team object (including accountId, avatarUrl, name, and id). When constructing the payload for jira-atlassian-work-item-create or update, it passes that full map instead of extracting just the single string representation (id or ARI). Because this serialization step happens inside Atlassian's shared tool invocation layer, prompt instructions like "pass only the team ID" are ignored—the prompt cannot override the tool payload formatting.

Known Workarounds

Since prompt engineering cannot fix the underlying API payload, here are the workarounds currently used by teams facing this issue:

Workaround 1: Make the Team field non-mandatory during creation (If applicable)

If the Team field is set to Required in your project's Field Configuration:

* Go to Project Settings > Fields (or Field Configuration).
* Set Team to Optional.
* When using Rovo Chat, explicitly ask Rovo to leave the Team field blank during creation.
* Set the Team manually after the ticket is created, or set up a Jira Automation Rule to assign the Team automatically based on the project or creator.

Workaround 2: Use Jira Automation as a middleman for Custom Agents

If you are using a Rovo Custom Agent, you can bypass the native jira-work-item-create action by delegating the creation to Jira Automation:

* Create a Jira Automation rule triggered by an incoming Webhook or a specific trigger event (e.g., a specific component/label added).
* Have the Rovo Agent invoke the Webhook/Automation action with a payload containing the raw teamId string.
* The Automation rule extracts the teamId smart value and creates/updates the issue cleanly.

Workaround 3: Create without context / strip context reference

If you are running Rovo chat directly inside an issue panel, Rovo automatically injects the parent item's field values (including the complex Team object) into its memory.

* Open Rovo Chat from the global navigation header (or a neutral page) rather than directly within an issue panel that already has a Team assigned.
* Provide only the project key and required text in the prompt without attaching or referencing existing context tickets.