-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
None
-
Affects Version/s: 10.0.0, 10.3.1, 10.3.2, 10.4.0
-
Component/s: Data Center - Apps
-
None
-
10
-
3
-
Severity 1 - Critical
-
8
Issue Summary
In a Jira instance running the Slack for Jira Data Center (official) integration, the Slack panel will show "Error getting Slack data from Jira" in the Issue View page.
Steps to Reproduce
- Install Jira 10+
- Install the Slack for Jira Data Center (official) add-on (v4.0.0 or 4.0.1, the ones compatibles with Jira 10)
- Configure the Slack integration
- Open an issue in the Issue View page and verify the Slack panel.
Expected Results
The Slack panel will display the Slack channels:
Actual Results
The following error is presented while loading the panel:
The below exception is thrown in the atlassian-jira.log:
A MultiException has 3 exceptions. They are: 1. org.glassfish.hk2.api.UnsatisfiedDependencyException: There was no object available for injection at SystemInjecteeImpl(requiredType=UserManager,parent=IssuePanelResource,qualifiers={},position=3,optional=false,self=false,unqualified=null,1086916793) 2. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of com.atlassian.jira.plugins.slack.web.rest.IssuePanelResource errors were found 3. java.lang.IllegalStateException: Unable to perform operation: resolve on com.atlassian.jira.plugins.slack.web.rest.IssuePanelResource A MultiException has 3 exceptions. They are: 1. org.glassfish.hk2.api.UnsatisfiedDependencyException: There was no object available for injection at SystemInjecteeImpl(requiredType=UserManager,parent=IssuePanelResource,qualifiers={},position=3,optional=false,self=false,unqualified=null,1086916793) 2. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of com.atlassian.jira.plugins.slack.web.rest.IssuePanelResource errors were found 3. java.lang.IllegalStateException: Unable to perform operation: resolve on com.atlassian.jira.plugins.slack.web.rest.IssuePanelResource
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
