Community
Q&A
Rovo
Questions
Is my Rovo Agent failing to create work items due to new Custom Field permissions?

Is my Rovo Agent failing to create work items due to new Custom Field permissions?

Hi everyone,

I’m using a Rovo Agent to create Jira work items in my project. This agent worked perfectly until recently, but now it fails with the error: Failed to create Jira Issue with any field.

I noticed that after Atlassian introduced the feature allowing agents to write to custom fields, the agent’s workflow changed. Previously, it would:

1. Search Jira Projects

2. Get Issue Type

3. Create Work Item

Now, it introduced a new step:

1. Search Jira Projects

2. Get Issue Type

3. Get Creatable Fields in Jira

4. Create Work Item

The failure seems to occur at the "Get Creatable Fields in Jira" step, when I debug I can see the result of that step is: Tool output data: Failed to invoke action. I suspect this might be related to new permissions required for accessing custom fields.

My questions:

1. Has anyone else experienced this issue with Rovo Agents after the custom field update?

2. Does the new “Get Creatable Fields in Jira” step require additional permissions?

3. What specific permissions or configuration should I ask my Jira admins to check or update to resolve this?

Any guidance or official documentation links would be greatly appreciated before I reach out to my Jira admins, as they are not very familiar with Rovo or its integration requirements.

Thank you!

2 answers

1 accepted

3 votes

Answer accepted

Hi @analaura_mora.

Currently, this is a Rovo limitation. No permission change will resolve it. To date, Rovo supports updating only the Summary and Description fields, regardless of the skills.

The ability to create and edit work items with required and/or custom fields will be rolled out soon. The failure you are seeing is likely due to ongoing updates to Rovo to add new functionality, but the functionality we need is not yet fully implemented.

You can search for two questions I previously posted that are similar to yours, and review the detailed answers I received.

You can also review, vote, watch, and comment on the relevant Rovo Suggestion issues here:

Talking with other Community Champions, it was @Dr Valeri Colon _Connect Centric_ who gave me the most crucial insight into how Rovo Agents execute prompts. Here is his insightful reply:

"What you're seeing is a current Rovo limitation, not a permissions problem on your side. Rovo Agents do not run as you, and they don't inherit your admin rights. They execute actions using Atlassian-managed service identities and only through the fields exposed by the specific skill. Today, the Jira "Update work item" skill reliably supports standard fields like Summary and Description, but custom fields such as Story Points are not consistently writable, even if they're on the screen and you're an admin.

There's no way to grant Rovo extra permissions via a service account, OAuth, or API token—Rovo can't be re-bound to a different identity. The agent's explanation about "bots/apps" reflects generic Jira automation concepts, not something you can configure for Rovo today.

So yes: this is a product limitation. Until Atlassian expands skill-level support for custom fields (which is actively being worked on), Story Points and similar fields will still require manual updates or Jira Automation rules as a workaround."

I have started pursuing the automation route and have had some success. Once the functionality is available in Rovo, I will switch back to prompts that are Agent with no Triggers.

I know this does not solve the issue, but I hope it helps.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @Don Hames,

Thank you for your detailed answer! Over the past couple of weeks, my team has also been relying on Jira automations to update custom fields after issue creation. This approach worked well until recently, when I started encountering the error I mentioned in my post.

I’ve been closely monitoring the Support creating work items with required/custom fields for some time now, and coincidentally, the error started appearing around the same time the feature was rolled out to 100% for Agents. With some further testing in our space, I've confirmed that my agent is now able to write to custom fields. Interestingly, the error occurs when I click the "Create" button directly, but if I use the "Edit" button to open the UI create panel and then click Create from there, the ticket is created successfully. This workaround is at least keeping us moving for now.

I agree with your assessment, this seems to be a side effect of the recent updates to support custom fields. Hopefully, it will be resolved soon.

Thanks again for your help and for sharing those useful links!