Rovo agent not creating ticket

[Raj]

I am trying to create a Rovo agent which can create tickets. But Rovo agent fails to create a ticket due to asset fields it is failing to retrieve the value and update the field as they are mandatory. How can we byspass this or how can we get the Rovo agent to pick the asset value and create the ticket.

[Tomislav Tobijas · Accepted solution]

Hi @Raj ,

This is, I would say, a known limitation. There's a feature request related to it: ROVO-229: Support creating work items with required/custom fields 👈

You can check the comments for any workaround , but I believe the team is currently working on supporting this functionality, so it might be rolled out soon.

Cheers,
Tobi

[Dr Valeri Colon _Connect Centric_]

@Raj  welcome to the community. You’re hitting a real limitation—Rovo struggles with required fields, and Assets fields are one of the hardest since they require valid object IDs (not just text). Right now, Rovo can’t reliably:

• Look up Assets values
• Select the correct object
• Populate required Assets fields

Workarounds:

• Create a simplified request type without required Assets fields
• Or use Automation: let Rovo create the ticket, then populate Assets afterward

This isn’t just prompt tuning—it’s a current product gap.

[Christopher Yen]

Hi @Raj welcome to the community!

With Rovo it has been a lot of trial and error but I believe the options here are either writing out instructions in your agent prompt to guide the agent on how to fill the required fields and testing and modifying until successful or create a new request type for your Rovo agent to use that has more lenient requirements.