Unable to load Advanced Roadmaps plans after Jira upgrade
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
After upgrading Jira Data Center, Advanced Roadmaps plans may fail to load and plan-related fields display rendering errors when searching for issues.
Diagnosis
The application log shows following error
2026-04-09 12:05:40,339+1200 http-nio-8080-exec-15 ERROR XXXXX XXXXX XXXXX XXXXXXXX /rest/jpo/1.0/backlog [c.a.r.c.r.provider.exception.DefaultExceptionMapper] Failed to retrieve issues
com.atlassian.rm.jpo.issueloading.model.IssueRetrievalException: Failed to retrieve issues
at com.atlassian.rm.jpo.issueloading.retriever.CompositeIssueRetriever.retrieveIssues(CompositeIssueRetriever.java:89)
at com.atlassian.rm.jpo.issueloading.DefaultIssueSearchService.getIssues(DefaultIssueSearchService.java:42)
at com.atlassian.rm.jpo.core.issue.DefaultCalculationAwareIssueService.getIssues(DefaultCalculationAwareIssueService.java:124)
at com.atlassian.rm.jpo.rest.service.backlog.BacklogRestEndpoint.get(BacklogRestEndpoint.java:215)
Caused by: java.lang.NumberFormatException: string is the wrong size
at com.atlassian.jira.search.utils.NumberUtils.stringToLong(NumberUtils.java:80)
at com.atlassian.jira.issue.statistics.TimeTrackingStatisticsMapper.loadValue(TimeTrackingStatisticsMapper.java:25)
at java.base/java.util.Optional.map(Optional.java:260)
at com.atlassian.jira.search.Document.getValue(Document.java:71)
at com.atlassian.jira.issue.DocumentIssueImpl.getSingleValueFromField(DocumentIssueImpl.java:115)
at com.atlassian.jira.issue.DocumentIssueImpl.getEstimate(DocumentIssueImpl.java:378)
The stack trace indicates an invalid time tracking or remaining estimate value when retrieving issue data from the search index.
Cause
This issue occurs because the search index contains invalid or incompatible time tracking or estimate data formats following the upgrade. The Advanced Roadmaps backlog components cannot parse these values from the index, leading to a java.lang.NumberFormatException: string is the wrong size.
Solution
To resolve this issue, perform a full re-index of your Jira instance. This ensures that all issue data, including time tracking and Advanced Roadmaps custom fields, are correctly mapped and stored in the search index.
Follow these steps to run a full re-index:
Log in as a user with the Jira Administrators system permission.
Go to Administration, then System.
In the left panel, select Indexing.
Select Full re-index.
Choose Re-index to start the process.
Once the indexing is 100% complete, navigate to Plans and verify that your plans load correctly.
Search for issues in the Issue Navigator to confirm that plan-related fields no longer display rendering errors.
Was this helpful?