"500 Internal Server Error" when deleting or opening a plan in Jira DC Advanced Roadmaps
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Users encounter a "500 Internal Server Error" when attempting to delete or open an existing plan.
Diagnosis
The following errors are noticed in the "atlassian-jira.log" file:
2026-01-01 04:04:08,082+0200 http-nio-8080-exec-1 ERROR [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] in context with path [] threw exception [java.lang.RuntimeException: Error while adding issue sources to JQL] with root cause com.atlassian.jira.util.dbc.Assertions$NullArgumentException: clause should not be null!
at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:25)
at com.atlassian.jira.jql.builder.DefaultJqlClauseBuilder.addClause(DefaultJqlClauseBuilder.java:633)
at com.atlassian.rm.jpo.issueloading.jql.JqlQueryGenerator.addIssueSources(JqlQueryGenerator.java:184)
at com.atlassian.rm.jpo.issueloading.jql.JqlQueryGenerator.addClause(JqlQueryGenerator.java:104)
at com.atlassian.rm.jpo.issueloading.jql.JqlQueryGenerator.buildJqlResult(JqlQueryGenerator.java:64)
at com.atlassian.rm.jpo.core.issue.DefaultJqlQueryService.buildJqlFromRequestData(DefaultJqlQueryService.java:221)
at com.atlassian.rm.jpo.core.issue.DefaultJqlQueryService.buildJQL(DefaultJqlQueryService.java:112)
at com.atlassian.rm.jpo.issueloading.retriever.ProjectIdRetriever.getProjectIds(ProjectIdRetriever.java:37)
at com.atlassian.rm.jpo.issueloading.DefaultIssueProjectService.getProjectIds(DefaultIssueProjectService.java:22)
at com.atlassian.rm.jpo.core.issuesource.context.DefaultIssueSourceContextService.extractProjectIdsFromIssueSourcesWithoutLimit(DefaultIssueSourceContextService.java:197)
at com.atlassian.rm.jpo.core.issuesource.context.DefaultIssueSourceContextService.extractProjectIdsFromIssueSources(DefaultIssueSourceContextService.java:138)
at com.atlassian.rm.jpo.core.issuesource.context.DefaultIssueSourceContextService.getProjectIdsForPlan(DefaultIssueSourceContextService.java:87)
at com.atlassian.rm.jpo.plugin.views.plan.common.CachedPlanInformationComponent.load(CachedPlanInformationComponent.java:82)
Cause
The affected plan is associated with a missing Issue Source (that is, Board or Filter).
Solution
Follow these steps in sequence to resolve the issue:
Stop Jira
Choose a working board with an operational filter. Following SQL can be used to identify the details:
SELECT b."ID", b."NAME" FROM "AO_60DB71_RAPIDVIEW" b WHERE b."NAME" = '<your exact working board name>';Note the ID returned by the SQL query above
Run the select command against the "AO_D9132D_ISSUE_SOURCE" table to get the ID of the broken boards :
SELECT * FROM public."AO_D9132D_ISSUE_SOURCE";Update the plan’s issue source to point to the new board:
UPDATE "AO_D9132D_ISSUE_SOURCE" SET "SOURCE_VALUE" = '<NEW_BOARD_ID from the first query>' WHERE "PLAN_ID" = <your broken plan ID from the second query> AND "SOURCE_TYPE" = 'Board' AND "SOURCE_VALUE" = '<add the old SOURCE_VALUE info here> '; COMMIT;Restart Jira and verify whether the plan is available now
If it appears, repeat the process for the other plans
The issue source can later be changed directly from the UI when the plan is accessible
Was this helpful?