-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
3.2.0-OD-07, 3.2.0
-
9
-
Severity 3 - Minor
-
0
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
Project permission cannot be edited after deactivating JIRA Service Desk as the permissions Service Desk Customer - Portal Access became Unknown security type (sd.customer.portal.only)
Steps to Reproduce
- Give any permissions to Service Desk Customer - Portal Access
- Deactivate JIRA Service Desk
- Try to edit the permission scheme again
Expected Results
Permission scheme loads upon edit
Actual Results
Permission scheme becomes blank
The below exception is thrown in the jira log file:
2016-04-08 08:07:47.633805500 2016-04-08 08:07:47,622 http-nio-3005-exec-13 ERROR sysadmin 487x38780x3 kiq6n2 104.192.142.137 /rest/internal/2/managedpermissionscheme/10003 [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null 2016-04-08 08:07:47.633807500 java.lang.NullPointerException 2016-04-08 08:07:47.633808500 at com.atlassian.jira.permission.management.ManagedPermissionSchemeHelperImpl.buildGrants(ManagedPermissionSchemeHelperImpl.java:317) 2016-04-08 08:07:47.633808500 at com.atlassian.jira.permission.management.ManagedPermissionSchemeHelperImpl.lambda$generatePermissionSchemeBean$4(ManagedPermissionSchemeHelperImpl.java:224) 2016-04-08 08:07:47.633853500 at com.atlassian.jira.permission.management.ManagedPermissionSchemeHelperImpl$$Lambda$1283/2703059.apply(Unknown Source) 2016-04-08 08:07:47.633853500 at com.google.common.collect.Iterators$8.transform(Iterators.java:799) 2016-04-08 08:07:47.633854500 at com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48) 2016-04-08 08:07:47.633859500 at com.google.common.collect.Iterators.addAll(Iterators.java:362) 2016-04-08 08:07:47.633859500 at com.google.common.collect.Lists.newArrayList(Lists.java:160) 2016-04-08 08:07:47.633860500 at com.google.common.collect.Lists.newArrayList(Lists.java:144) 2016-04-08 08:07:47.633866500 at com.atlassian.jira.permission.management.ManagedPermissionSchemeHelperImpl.generatePermissionSchemeBean(ManagedPermissionSchemeHelperImpl.java:238)
Workaround
Use a different permission scheme.
- duplicates
-
JSDSERVER-3324 Update Service Desk Documentation to Reflect that Project Permissions are Not As Relevant
- Closed
- relates to
-
-
- Closed
-
- links to
- was cloned as
-
QUALITY-507 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-3640] Project permissions cannot be edited once JIRA Service Desk is Deactivated
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: affects-cloud affects-server cqt ril | New: affects-cloud affects-server cleanup-seos-fy25 cqt ril |
| Labels | Original: affects-cloud affects-server cqt | New: affects-cloud affects-server cqt ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 954886 ] |
| Support reference count | Original: 7 | New: 9 |
| Support reference count | Original: 9 | New: 7 |
| UIS | Original: 1 | New: 0 |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304236 ] | New: JAC Bug Workflow v3 [ 3126430 ] |
| Status | Original: To Do [ 10071 ] | New: Gathering Impact [ 12072 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center