Why is there a response difference when prompting a Rovo agent via Jira Automation vs. in Rovo Chat

[엄성렬]

Hey everyone,

I've created a Rovo agent and used prompt engineering so that when I provide a Jira ticket key (e.g., TEST-111), it reads the ticket and responds with relevant keywords in the format A,B,C to be used as labels. If no relevant keywords are found, it's supposed to respond with N/A.

However, I'm seeing a difference in the response when I give the prompt TEST-111 to the agent through Jira Automation versus when I give the same prompt in the Rovo agent's chat interface.

• In Jira Automation, the agent returns N/A, as if it can't find the information.

• In the Rovo Chat, the agent correctly returns the keywords as A,B,C.

Can anyone explain why this is happening?

[Bill Sheboy]

Hi @엄성렬 -- Welcome to the Atlassian Community!

Without seeing your entire automation rule and its audit log details...

Perhaps there is an update or timing problem in the rule and thus the work item's data is not matching for the different scenarios you describe.  Seeing the rule and audit log may help clarify this symptom.

Kind regards,
Bill

[엄성렬]

Hi @Bill Sheboy 

Here is my rule and audit log and chat.

 

I hope this provides the clarity needed to diagnose the symptom. Please let me know if you need any other details from my end. Thanks again for your help!

Best regards,

Sungryul Eom

[Bill Sheboy]

Thanks for that information.

I have seen questions with timing problems with Rovo agents where first storing the {{agentResponse}} in a created variable allowed better access, although I would not expect that to be a problem when logging the value.

I recommend working with your site admin to submit a ticket to Atlassian Support to take a look: https://support.atlassian.com/contact/#/

And when you hear back from them, please post what you learn to benefit the community.  Thanks!

[Mariia Novhorodtseva]

….