-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: 1.5
-
Component/s: Integration - JIRA
-
None
-
Environment:
Jira's configuration:
External user management ON
Crowd integration ON
When a user in Jira runs a search looking for unassigned issues, and tries to save the search, the handles function in CrowdCredentialsProvider is called, and throws the following exception:
java.lang.IllegalArgumentException: Null argument passed to method!
at com.atlassian.crowd.integration.util.Null.not(Null.java:9)
at com.atlassian.crowd.integration.osuser.CrowdCredentialsProvider.handles(CrowdCredentialsProvider.java:162)
at com.opensymphony.user.UserManager.getProvider(UserManager.java:313)
at com.opensymphony.user.UserManager.getEntity(UserManager.java:299)
at com.opensymphony.user.UserManager.getUser(UserManager.java:193)
at com.atlassian.jira.user.util.UserUtilImpl.getUser(UserUtilImpl.java:241)
at com.atlassian.jira.plugin.profile.ProfileLinkUserFormat.getInitialParams(ProfileLinkUserFormat.java:46)
at com.atlassian.jira.plugin.profile.ProfileLinkUserFormat.format(ProfileLinkUserFormat.java:38)
at com.atlassian.jira.plugin.profile.DefaultUserFormatManager.formatUser(DefaultUserFormatManager.java:48)
...
The Null.not check was not done in Crowd 1.3, so with 1.3, the same functionality (saving searches for unassigned issues) was working properly. After an upgrade to 1.5, customers will experience the previous exception when trying to save searches for unassigned issues.
- causes
-
-
- Closed
-
- is caused by
-
-
- Closed
-
