-
Bug
-
Resolution: Fixed
-
Highest
-
5.4.0, 4.20.15, 5.3.2, 5.4.1, 5.5.1, 5.4.2
-
32
-
Severity 3 - Minor
-
431
-
Issue Summary
User receives the following error message when accessing Project settings if no object schema exists and user is not part of the jira-systems-administrators group:
Sorry, you do not have permission to perform this action.. PermissionInsightException: User XXXXXXX didn't have correct permission Sorry, you do not have permission to perform this action.
This only affects project administrators. On pages that have nothing related to Assets.
REST Call: <jira_base_url>/rest/insight/1.0/global/config Returns -> 403 causing the error
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create a project in a JSM system with Assets bundled
- Create a normal user
- Assign new user as Project Lead and Project administrator
- Login as this user
- Access the assigned Project's Project Settings page
Expected Results
No error if Assets is not in use
Actual Results
PermissionInsightException exception reporting user does not have permission
Workaround
Create a blank Assets Schema should be enough to bypass the problem, but if that is not your case, proceed to the following steps:
1- As a Jira Admin, click on ‘Assets’ and create am Empty Object Schema;
2- While on Assets >> Object Schemas, click on Configure >> Roles for that particular Object Schema you just created
3- Add the desired user or group to one of the roles
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-12199] Access Project Settings results in PermissionInsightException
I´m getting a lot of these warnings on Jira DC v9.4.3, so dont think this is solved.
I've found the "Assets Plugin", but in 9.4/5.4 the option to disable it isn't there. What I'm running into, is project admins that don't have a JSM license are getting this error.
These apps are integral parts of your JIRA application(s). They cannot be disabled or uninstalled. You may uninstall applications from the Versions & licenses page.
All,
There is a plugin called "Assets Plugin" that gets installed by default with the new versions of JSM, go ahead and disable it in the UPM and that will resolve your problem.
We have on-premise Jira software version 9.4.1, we manually upgraded only jira service management to 5.4.2.
Still the same error is occurring.
Sorry, you do not have permission to perform this action.. PermissionInsightException: User userid didn't have correct permission Sorry, you do not have permission to perform this action.
And we don't even have Insight licensed (Server) and this issue started appearing. Since we don't have a license, the workaround here to create a blank asset doesn't work for us.
Hi 37e1a2f066c3
I'm one of the Support Engineers for Jira On-Prem and I specifically focus on Assets (Insight).
Can you please log a support ticket with us and send us a support zip so we can double-check your environment and confirm if the issue is indeed not resolved correctly?
Kind Regards,
Jarrod Price
Jira On-Prem Support, EMEA
ATLASSIAN
Hi,
While JSM 4.20.17 has resolved https://jira.atlassian.com/browse/JSDSERVER-12213 - this JAC is still an issue
- A project admin attempts to view the Project Summary page - eg: https://jira.company.com/plugins/servlet/project-config/PROJ/summary
- If the user does not have access to any insight schemas, they will be shown a popup error "Error Sorry, you do not have permission to perform this action.. PermissionInsightException: User JIRAUSER12345 didn't have correct permission Sorry, you do not have permission to perform this action."
- We do not want to have to create a blank globally accessible Insight Schema to bypass this issue - and given the fixVersion of 4.20.17 was tagged, we expected this issue to be resolved
If we can get an ETA on a proper fix as this is confusing our project admins
CCM
As my customer has Jira Server 8.20.15 and gets exactly this Error Message when trying to Export Asset Objects, I assume it is the same root cause?
Test environment on Jira Server 8.20.14 does not have that problem
Can confirm that it still persists in 9.4.5