-
Bug
-
Resolution: Fixed
-
Low
-
2.2.2, 2.6.1
-
Severity 2 - Major
-
NOTE: This bug report is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding bug report.
When attempting to load a plan, users are presented with a 500 error page:
Expanding this for more details show a long trace:
Technical details Log's referral number: 6ab881f9-52a8-4dcd-ad79-56c30dff463b Cause Referer URL: Unknown com.atlassian.jpo.env.jql.IssueSourceTranslationException: Invalid JQL or unable to translate. com.atlassian.jpo.env.jql.IssueSourceTranslationException: Invalid JQL or unable to translate. at com.atlassian.jpo.env.jql.JiraJqlIssueSourceTranslator.translate(JiraJqlIssueSourceTranslator.java:85) at com.atlassian.jpo.env.projects.JiraProjectAnalysisService.getProjectIdsForIssueSources(JiraProjectAnalysisService.java:52) at com.atlassian.jpo.issuesource.context.DefaultIssueSourceContextService.getProjectIdsForIssueSourcesWithoutFallback(DefaultIssueSourceContextService.java:95) at com.atlassian.jpo.issuesource.context.DefaultIssueSourceContextService.extractProjectIdsFromIssueSourcesWithoutLimit(DefaultIssueSourceContextService.java:140) at com.atlassian.jpo.issuesource.context.DefaultIssueSourceContextService.extractProjectIdsFromIssueSources(DefaultIssueSourceContextService.java:122) at com.atlassian.jpo.issuesource.context.DefaultIssueSourceContextService.getProjectIdsForPlan(DefaultIssueSourceContextService.java:75) at com.atlassian.rm.jpo.plugin.views.plan.common.CachedPlanInformationComponent.load(CachedPlanInformationComponent.java:68) at com.atlassian.rm.jpo.plugin.views.plan.view.standard.PlanView.execute(PlanView.java:118) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:225) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:154) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) ... Caused by: com.atlassian.rm.common.env.EnvironmentServiceException: Unknown filter: 24562 at com.atlassian.jpo.env.jql.JiraJqlIssueSourceTranslator.translateFilter(JiraJqlIssueSourceTranslator.java:116) at com.atlassian.jpo.env.jql.JiraJqlIssueSourceTranslator.translate(JiraJqlIssueSourceTranslator.java:75) ... 204 more
Cause
- The plan is using an Agile board, which is then using a JQL filter that no longer exists or cannot be parsed.
Expectation
The plan is loaded, indicating that the data has changed or is no longer available. It would show the configuration details of which Agile board is referenced or filter ID is being used.
Actual
The 500 page is presented and the user will have no course of action to understand how to fix the issue or what caused it.
Workaround
- Fix the filter being referenced by the Plan and ensure it is valid
- If plugin functionality is referenced, ensure that the plugin is installed and enabled or remove the plugin functions in the JQL
- If the filter is no longer available, create a new filter and update the database, setting the new filter's ID to be the same as the originally referenced ID. A restart of JIRA is required after the change
Additional Details
This error only occurs when the broken filter is associated with a JIRA Software board and that board is referenced by the plan. It does not occur when the plan directly references the broken filter.
- Different error appears when the plan directly references filter with invalid JQL (JqlParseException)
- When the filter is completely missing the plan will continue to load but without the board as an issue source.
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-