-
Bug
-
Resolution: Obsolete
-
Low
-
None
-
2.1.1
-
Severity 3 - Minor
-
Problem
Currently installing JIRA Service Desk also installs Atlassian Chaperone. These are interdependent but disabling one won't disable the other altogether.
If an admin disables Atlassian Chaperone, accessing a Service Desk will result in an Internal Server Error (500) page with the following stacktrace:
com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:124) at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:52) at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) ... Caused by: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Required plugin module com.atlassian.plugins.atlassian-chaperone:chaperone was either missing or disabled at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2234) at com.google.common.cache.LocalCache.get(LocalCache.java:3970) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4834) at com.google.common.cache.LocalCache$LocalManualCache.getUnchecked(LocalCache.java:4839) ...
Steps to Reproduce
- Install JIRA Service Desk
- Create a new Service Desk
- Disable Atlassian Chaperone
- Try to access the Service Desk
Workaround
Do not disable Atlassian Chaperone. If it is disabled, re-enabling it should make the Service Desk accessible again.
However, if the plugin is uninstalled, then JIRA Service Desk will be disabled and can't be re-enabled. In this case, users can only uninstall JIRA Service Desk and re-install it, which will also re-install Atlassian Chaperone.
Suggestion
Dependent plugins of JIRA Service Desk should be made unmodifiable and rely on the status of JIRA Service Desk itself.
- incorporates
-
-
- Closed
-
- relates to
-
JSDSERVER-1033 Uninstalling Service Desk should uninstall its dependencies as well
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-1246] Disabling Atlassian Chaperone causes Service Desk to stop working
After creating the Service desk project, I was shown the error 500 page corresponding to the welcome page for service desk.
Jason Schwanz
added a comment - It's very difficult to know what add-ons are dependencies for other add-ons. There definitely needs to be a way for this information to be easily discovered.
Jason Schwanz
added a comment - It's very difficult to know what add-ons are dependencies for other add-ons. There definitely needs to be a way for this information to be easily discovered. I believe this is something that should definitely be put up in priority. While many may not vote for this until they run into it, it should be implemented before administrators do this. A coworker wasn't as knowledgeable, but was trying to "enhance" speed by disabling what they thought were unused "add-ons".
Hello All,
This defect seems obsolete now, given that Jira Service Desk is offering version 3.9 currently. If you encounter a similar issue on your recent versions, please feel free to create a new bug with relevant details.
Cheers,
Vidhu Sharma
Product Manager - Jira Service Desk