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?

[Andy Heinzer]

Hi @엄성렬 

I created a support case on your behalf in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-1162417

[G subramanyam]

Hi @엄성렬 welcome to the Atlassian Community.

The behavior you're observing strongly suggests a difference in the context, permissions, or data access scope of your Rovo agent when it's invoked by Jira Automation versus when you interact with it directly in the Rovo chat interface.

Let's break down the likely reasons and what you can check:

1. Authentication and Permissions Context: The Rovo agent, in this scenario, likely accesses Jira data using your permissions or a connection that leverages your authenticated session. If you can manually see the issue and its details in Jira, the Rovo agent effectively "sees" it through your eyes.

• When a Jira Automation rule runs and uses the "Use Rovo Agent" action, the Rovo agent doesn't necessarily inherit your personal Jira permissions. Instead, it typically accesses Jira data using:

•      A dedicated API key/token

•      service account

    2. Even if the Rovo agent has some permissions, the scope might be limited

You'll need to investigate the connection and permissions of your Rovo agent's integration with Jira.

Note: One of the Rovo's users have shared these points when checked about your query.

[엄성렬]

Hi @G subramanyam  Thank you for the quick and detailed reply.

Your explanation regarding the permissions and context makes a lot of sense. I have a few follow-up questions and have attached a screenshot of the permissions menu for my Rovo agent.

1. To grant the necessary permissions, should I add the "Browse projects" permission in the menu shown in this screenshot?
2. If I want to grant access to Confluence as well, would I follow the same process here? Or is there a different or better way to configure this?
3.  I am not a Jira administrator, I will need to request this permission change from our admin team. To ensure my request is accurate, could you please tell me the exact name of the permission group or role that the Rovo agent needs to be added to? For example, should I ask the admin to add the agent to a specific group named something like rovo-agents-admin, or is it a different name? This will help me provide a clear and precise request to our administrator.

Any further guidance would be greatly appreciated.

[G subramanyam]

Hi @엄성렬 I have requested for Atlassian team support to provide accurate details that benefits you task. One of them will connect with you on this thread.