We have a case in which the Two Dimentional Filter Statistics gadget doesn't manage to retrieve a filter (due to a NullPointer exception in the logs) when accessed by a not logged-in user. We get the following error:
"The filter configured for this gadget could not be retrieved. Please verify it is still valid on the issue navigator."
See attachments for screenshots and exceptions in the log.
However, if I run the filter over UI it works correctly, so it's accessible by anonymous.
If there is a user logged in the gadget shows correcly.
The issue occurs when the gadget is configured to filter on a custom field, which uses a "Exact Text Searcher (natural)" searcher, provided in Natural Searchers for JIRA.
Below is the exception in logs.
2015-09-22 08:17:26,231 http-bio-8080-exec-15 ERROR anonymous 497x31248x2 590yqe 10.57.27.188,10.228.247.68 /rest/gadget/1.0/twodimensionalfilterstats/generate [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null java.lang.NullPointerException at sk.eea.jira.searchers.natural.ExactTextStatisticsMapper.getSearchRequestAppender(ExactTextStatisticsMapper.java:84) at sk.eea.jira.searchers.natural.ExactTextStatisticsMapper.getSearchUrlSuffix(ExactTextStatisticsMapper.java:55) at sk.eea.jira.searchers.natural.ExactTextStatisticsMapper.getSearchUrlSuffix(ExactTextStatisticsMapper.java:14)
JIRA version is 6.4.11
Downloaded the code and updated the code to do a null check for anonymous access. Now it works.
Would you mind elaborating on how you implemented your null check? We are hitting the same issue- users who are logged out cannot see the results of our filter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joseph,
I just did a null check in the method that is throwing the exception.
@Override public SearchRequestAppender<String> getSearchRequestAppender() { if(authenticationContext.getUser() == null) { return new ExactTextSearchRequestAppender(customFieldInputHelper.getUniqueClauseName(null, customField.getClauseNames().getPrimaryName(), customField.getName()), Operator.EQUALS); } return new ExactTextSearchRequestAppender(customFieldInputHelper.getUniqueClauseName(authenticationContext.getUser().getDirectoryUser(), customField.getClauseNames().getPrimaryName(), customField.getName()), Operator.EQUALS); }
customFieldInputHelper is not throwing the null when the user passed is null.
Regards,
Vijay.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.