The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

403 error loading component for LookupObjects

Peter Makki
January 10, 2024

As in the title, I've got 403 when I try to add "lookup objects". I've tried to reload page, to enable cookies, to relogging - still the same error.

 

Has anyone encountered that? 

403atlassianautomatian.jpg

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
adam
Contributor
July 10, 2024

Hi guys,

i have the same problem. Automation in cloud works fine, but with the "lookup objects" i get the 403 error.

Any tips?

thanks & regards

Radek Pouč
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!
July 10, 2024

Hi Adam,

403 error code stands for access forbidden - you need to have a JSM agent licence in order to see the object.

adam
Contributor
July 10, 2024

Hi @Radek Pouč

hm i do have the JSM agent licence. And the rule is not specific for something in JSM, i just wanted to explore the possibilitys with lookup objects.

0 votes
Radek Pouč
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!
January 23, 2024

Hello Peter,

I have encountered this exact issue today. The solution for this is simple. 403 error code stands for access forbidden - you need to have JSM agent licence in order to see the object. Adding JSM agent licence for myself fixed this issue.

Radek

TAGS
AUG Leaders

Atlassian Community Events