Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When the users login into their projects ,we are seeing a weired error message

When the Jira user trying to access their projects,They will be able to access,But in the right side corner,they can see a weired error meaasege.

Could you please help us,what is this message for.


Errormsg: Sorry you don't have permission to perform this action.

PermissionInsightException:User vboddu didn't have correct permission.


Every Jira user is seeing  this InsightException error >please help us.

1 answer

0 votes
Brant Schroeder Community Leader Jan 25, 2023

@Venky Boddu Welcome to the Atlassian community

Have you looked at the logs to see if there is more information about what is causing the error?  Most likely there is a permission that is missing and the logs should help point out which one.  

Brant Schroeder Community Leader Jan 25, 2023

@Venky Boddu Can you also share a screenshot of the error?

We tried to capture the error in the Logs.We couldn't find any.


As per this document,This may be a bug.


[JSDSERVER-12199] Access Project Settings results in PermissionInsightException - Create and track feature requests for Atlassian products.

Brant Schroeder Community Leader Jan 25, 2023

@Venky Boddu did you try the workaround listed in the link above to resolve the issue?  

Suggest an answer

Log in or Sign up to answer