Forbidden Error message: Permission Issue.

Hello all... This is my second question and I want to say thanks to all that help.

Myself and other users are getting the error message I will attach quite frequently. We are all Admin level and can see and do everything. The message does not block access, rather its an annoyance. Any ideas on how to fix it or stop the message????

2 answers

0 votes

Admin is irrelevant to whether you can see stuff. Admin gives you admin rights, not access to everything (unless you, as an admin, change the permissions to allow admins to see everything)

Basically though, look at the permission scheme for the project. You've got it set up to allow "create" but not "browse" for the users.

I am logged in as an Admin, and I have admin rights to all projects and have all permissions to all projects. Still getting error.

Again, forget the admin stuff, it's irrelevant.

What does the permission scheme explicitly say for "Browse:"?

Neither areas have Users ability to access. I have created groups for outside users to access a view only to certain projects. If I add users to any of those permissions then as default the outside vendors will have abilities we dont want them to have. I hope this makes sense. I am still new at JIRA.

The group I created with users in it has the browse permission so they can see what we are working on and thats it.

"neither area has users ability to access" - that's probably it, but it is still very unclear what you have set up.

Please could you start from the basics, and stick to using the words Jira uses to avoid confusion.

  1. Go to the project and look at the permission scheme. What does it have next to "browse"?
  2. Once you have got the list of groups, roles or whatever who have "browse", then look at who matches those patterns. (e.g. if you have "browse: group: Penguins", then who is in the "penguins" group?)

Unfortunatly, The issue is different. All users in the system fall under one of the groups listed under browse in all of the permission schemes. They can all access what they need. Its more like a bug that is just a pain the the ass. Like I said earlier, it does not block access, it just pops up and when you hit continue you are able to access the issue or project etc... Its just a little bothersome and upper management asked me to investigate. Thanks for your input.

Ok, this is sounding like you have some form of network or user caching issue. Jira isn't getting the information that you are logged in as user X when you try to do something, but when you try it again, it's fine.

I'm afraid you need to establish a clear pattern first - when does it happen, are there specific users, are there specific actions that cause it and so-on.

Also, what user directory type are you using?

My team started experiencing the same issue this week - all was well until Tuesday (this is annoying).

What URL are you trying to follow when you get that message?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,769 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you