nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rovo accessing Jira Assets

Mario

Hi lovely community

I have set up assets bot to help with queries based on the assets skill ( I understand it's stil in beta" I tried doing some prompts but i get a error stating "The IT/Hardware assets schema (such as Schema 11) is restricted"

I have assigned the app (Assets) to the agent and have given it user access plus admin access within the app to the assets but I still get restricted as a error

So its not accesing our assets inventory within Jira, any suggestions?

Accepted answers

Matthew Sinclair

I seem to recall having a similar problem when creating a new assets custom field.

Check the field configuration and make sure the AQL and scope are correctly set.

I'm fairly confident you will find your problem solved that way.

I also used Rovo to talk me through it as well.😁

Ciro

Hey, good question.

That message usually means the agent isn't allowed into that schema, even with Assets added. I'd check two things:

The skill's schema scope. When you add the Search Assets data skill to an agent in Studio, you can limit which Assets schemas it can access. Open the agent, go to Edit > Skills and make sure the IT/Hardware schema is in that list.
Which account the agent runs as. If it uses the account of the person chatting, it only sees what that person can see in Assets, so they need a role on that schema (Assets > Schemas > the schema > Schema configuration > Roles; Object viewer is enough to read). If the agent uses its own agent account, that account needs the schema role instead. Schema roles are set per schema, so access to the Assets app alone doesn't open every schema to it.

The skill is still in beta and read-only for now, so if both look right and you still get "restricted", I'd raise it with support and include the agent name and the prompt.

All comments

Matthew Sinclair

I seem to recall having a similar problem when creating a new assets custom field.

Check the field configuration and make sure the AQL and scope are correctly set.

I'm fairly confident you will find your problem solved that way.

I also used Rovo to talk me through it as well.😁

Ciro

Hey, good question.

That message usually means the agent isn't allowed into that schema, even with Assets added. I'd check two things:

The skill's schema scope. When you add the Search Assets data skill to an agent in Studio, you can limit which Assets schemas it can access. Open the agent, go to Edit > Skills and make sure the IT/Hardware schema is in that list.
Which account the agent runs as. If it uses the account of the person chatting, it only sees what that person can see in Assets, so they need a role on that schema (Assets > Schemas > the schema > Schema configuration > Roles; Object viewer is enough to read). If the agent uses its own agent account, that account needs the schema role instead. Schema roles are set per schema, so access to the Assets app alone doesn't open every schema to it.

The skill is still in beta and read-only for now, so if both look right and you still get "restricted", I'd raise it with support and include the agent name and the prompt.

Mario

Hi Ciro

What will be the account called (Like is it Rovo) to be added to the Schema configuration? I tried searching for Rovo but got no results?

Mario

Ah I found something!

Mario

Within the Jira admin portal under Rovo > groups and add the user group attached to the agent to the Schema configuration

Mario

Thank Matthew! appreciate it

Matthew Sinclair

Glad to hear it was easier than my troubleshooting step - that took me a bit to learn haha

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

rovo-atlassian-intelligence

jira-assets