Rovo agent is not able to fill the assignee name

[Kondiboyina Khadri_ Hari Pradeep]

Hi Community, I am creating an agent to automate the jira creation with some mandatory fields and input assignee. The agent is able to resolve the accountId, but the assignee is still being automatic in the preview jira created by agent. I am using the following in the prompt. fields.assignee = { "accountId": "<ownerAccountId>" }
- fields.customfield_11.. = [ { "accountId": "<managerAccountId1>" }, { "accountId": "<managerAccountId2>" }, ... ] . What can be going wrong? I have tired with ari values as well. Same issue.

[Rebekka Heilmann _viadee_]

Hi @Kondiboyina Khadri_ Hari Pradeep - welcome to the Community,

to add to @A A Ron Geister _Trundl_ , you could check the history of the issue created to see if the assignee is being replaced by other rules.

If this isn't helping already, there could be a number of other reasons why Rovo isn't doing what's expected.

Could you give us a little more context? Are you calling the Agent from Chat or within an Automation? What does the prompt look like? Does the Agent have access to the correct skills?

[A A Ron Geister _Trundl_]

@Kondiboyina Khadri_ Hari Pradeep

It looks like the agent is resolving the accountId correctly, but Jira is still overriding the assignee. A couple things to check:

1. Use "id" instead of "accountId" for the assignee on issue creation.
Jira’s create API often ignores assignee:

"assignee": { "id": "

<ownerAccountId>" }

2. Project settings can override whatever you send.
If the project (or a component) has a default assignee or a workflow post‑function that sets the assignee, Jira will replace your value every time.

3. Make sure both the agent and the target user have Assignable User permissions.

If all of that checks out and Jira still auto‑assigns, the workaround is a two‑step flow: create the issue normally, then immediately call the “Assign issue” action with the accountId. That always sticks because it bypasses the create‑time overrides.