-
Bug
-
Resolution: Fixed
-
Low
-
2.5.9, 3.2.11, 3.8.1
-
5
-
Severity 3 - Minor
-
3
-
Hello Customers,
We’ve addressed this bug and the fix is available on all version of Jira Service Desk 3.9 and above. For more information please refer to the documentation here
Thank you, for your patience and support.
Jira Service Desk Team
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
JIRA doesn't allow Project administrators to change the Permission scheme associated to their projects if they do not have the JIRA Administrators Global Permission as well.
However, when a Project admin (not JIRA Administrator) creates a Service Desk for his project, he can migrate the permission scheme by clicking in the "Migrate this project" button.
Steps to reproduce
- Have a Project Administrator without JIRA Administrators global permission
- Create a Service Desk for an already existent project
- Open the new Service Desk
- An error is displayed stating the project is missing permissions with a "Migrate this project" button at the bottom.
Expected Behaviour
JIRA should not allow non-JIRA Administrator to click on the button.
Actual Behaviour
non-JIRA Administrator is able to successfully change the project's permission scheme by clicking on the button.
- is duplicated by
-
JSDSERVER-3267 Users without the proper Global Permissions should not be able to Upgrade the Permission Scheme
- Closed
- is related to
-
JSDSERVER-1721 Allow admins to customise JIRA Service Desk permission schemes
- Closed
- relates to
-
JSDCLOUD-905 Project administrator is able to migrate Permission Scheme
-
- Closed
-
-
JSDSERVER-334 Improve the migrate permission scheme process
- Closed
-
JSDSERVER-3267 Users without the proper Global Permissions should not be able to Upgrade the Permission Scheme
- Closed
[JSDSERVER-905] Project administrator is able to migrate Permission Scheme
Fixed in Enterprise Release/s | New: [Download 3.9|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2463962 ] | New: JAC Bug Workflow v3 [ 3126299 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Fix Version/s | New: 3.9.0 [ 74730 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To Do [ 10071 ] | New: Closed [ 6 ] |
Description |
Original:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-905]. {panel} JIRA doesn't allow Project administrators to change the Permission scheme associated to their projects if they do not have the JIRA Administrators Global Permission as well. However, when a Project admin (not JIRA Administrator) creates a Service Desk for his project, he can migrate the permission scheme by clicking in the "Migrate this project" button. *Steps to reproduce* # Have a Project Administrator without JIRA Administrators global permission # Create a Service Desk for an already existent project # Open the new Service Desk # An error is displayed stating the project is missing permissions with a "Migrate this project" button at the bottom. *Expected Behaviour* JIRA should not allow non-JIRA Administrator to click on the button. *Actual Behaviour* non-JIRA Administrator is able to successfully change the project's permission scheme by clicking on the button. |
New:
{panel:title=Atlassian status update as of 12th July 2018}
Hello Customers, We’ve addressed this bug and the fix is available on all version of Jira Service Desk 3.9 and above. For more information please refer to the [documentation here |https://confluence.atlassian.com/adminjiraserver/resolving-jira-service-desk-permission-errors-938847163.html] Thank you, for your patience and support. Jira Service Desk Team {panel} {panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-905]. {panel} JIRA doesn't allow Project administrators to change the Permission scheme associated to their projects if they do not have the JIRA Administrators Global Permission as well. However, when a Project admin (not JIRA Administrator) creates a Service Desk for his project, he can migrate the permission scheme by clicking in the "Migrate this project" button. *Steps to reproduce* # Have a Project Administrator without JIRA Administrators global permission # Create a Service Desk for an already existent project # Open the new Service Desk # An error is displayed stating the project is missing permissions with a "Migrate this project" button at the bottom. *Expected Behaviour* JIRA should not allow non-JIRA Administrator to click on the button. *Actual Behaviour* non-JIRA Administrator is able to successfully change the project's permission scheme by clicking on the button. |
Labels | Original: affects-server cqt cvss-medium mfd pm pse-request security | New: affects-server breaches-security-sla cqt cvss-medium mfd pm pse-request security |
UIS | Original: 6 | New: 3 |
Support reference count | New: 5 |
Priority | New: Low [ 4 ] |
Labels | Original: affects-server cqt cvss-medium mfd pse-request security | New: affects-server cqt cvss-medium mfd pm pse-request security |