Rovo Automation Rule Fails to Update Fields from JSON Response

Summary

A Jira automation rule using a Rovo Agent action appears to run successfully in the audit logs, but the subsequent "Edit Issue" or "Set Field" actions do not actually populate any data

Diagnosis

A Jira automation rule using a Rovo Agent action appears to run successfully in the audit logs, but the subsequent "Edit Issue" or "Set Field" actions do not actually populate any data. This typically happens when the Rovo Agent is instructed to return data in a structured JSON format, but the automation rule cannot parse the values correctly.

Symptoms:

• The automation audit log shows the rule executed successfully.

• The Rovo Agent response contains the expected data (e.g., in JSON format).

• Jira fields remain empty or unchanged after the rule runs.

• Audit logs may show warnings like: "We excluded the configured field from this action as it couldn't be found."

Cause

The issue is caused by an incorrect smart value invocation. By default, {{agentResponse}} treats the output as a single string.

If the Agent returns a JSON object, attempting to access a specific key using {{agentResponse."Key Name"}} will fail because the automation engine is looking for a property on a string rather than a JSON object.

Solution

Use Log action to verify the result of {{agentResponse}}

To correctly extract values from a JSON response provided by a Rovo Agent, you must use the appropriate smart values like .asObject property to tell the automation engine to parse the response as a JSON object.

Steps to Fix:

1. Update your Smart Values: Change your field mapping from: {{agentResponse."Your Field Name"}} To: {{agentResponse.asObject."Your Field Name"}}

2. Example: If your Rovo Agent returns:

{ "Request Type": "Support ticket", "IP Address": "1.1.1.1" }

Use {{agentResponse.asObject."Request Type"}} to populate the Request Type field in Jira.

1. Verify the Agent Prompt: Ensure your Rovo Agent instructions explicitly tell it to return only raw JSON without markdown code blocks (like ` ` `json ... ` ` `) to ensure the parser can read it cleanly.

Best Practices:

• Use Rovo Chat: For complex automation logic, use Rovo Chat to test your prompts and see how the JSON is structured before implementing it in a rule.

• Custom Agents: If your prompt is very large or complex, create a Custom Agent in Rovo Studio. This allows you to define specific instructions and tools, making the automation rule cleaner and more reliable.