Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Need help with Rovo Agent Response parsing

venkatasai.pulluri
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 2, 2025

Here is the Agent prompt:

Analyze this work item using the “Priority Reference for Defect Triage” article and project history.

Return ONLY valid JSON on a single line. No code fences, no explanations, no markdown.

Example:
{"priority":"High","reason":"API timeout after deployment; matches High rule per reference"}

Rules:
- The JSON must contain exactly two keys: "priority" and "reason".
- "priority" value must be exactly one of: Highest, High, Medium, Low.
- "reason" must be a short human-readable sentence (no quotes inside).
- Do not add spaces, line breaks, or any extra text before or after the JSON.


When i print the raw output i get it correctly:

Raw = {"priority":"Low","reason":"No summary or description details match any higher priority rule; defaulting to Low per reference"}

 

I am trying to return Priority and Reason as separate variables and they give output as empty

Raw = {{agentResponse}} Priority = {{jsonStringToObject(agentResponse).priority}} Reason = {{jsonStringToObject(agentResponse).reason}}

 

Priority =

Reason =

 

Can you help set the right json parsing for agent output. Based on it i want to assign right priority to ticket

3 answers

2 accepted

0 votes
Answer accepted
Rebekka Heilmann _viadee_
Community Champion
November 4, 2025

Hi  @venkatasai.pulluri - welcome to the Community,

Jensen just published an article on parsing of the AgentResponse: How to Use {{agentResponse}} in Atlassian Automati... - Atlassian Community

including a JSON option. Maybe that's helpful too?

0 votes
Answer accepted
Nikola Perisic
Community Champion
November 3, 2025
1 vote
Dr Valeri Colon (Connect Centric)
Community Champion
November 14, 2025

@venkatasai.pulluri to add to @Rebekka Heilmann _viadee_ and @Nikola Perisic resources: The agent output is valid, but Automation treats it as a string with hidden whitespace. Wrap the raw value in a trim before parsing:
{{jsonStringToObject(trim(agentResponse)).priority}}
and
{{jsonStringToObject(trim(agentResponse)).reason}}.
Once trimmed, the fields resolve correctly and you can map the priority.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events