Advanced Roadmap Plan not loading data

Still need help?

The Atlassian Community is here for you.

Ask the community


 

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

   

Summary

An Advanced Roadmaps Plan page attempts to load, but eventually times out and shows a red box with the error of:

Something went wrong.

Wait a few seconds, then try again. If this keeps happening, let us know at...


Environment

Jira Cloud

Diagnosis

On the red error message above, clicking View Log shows an error similar to:

Request Information
Url: /rest/jpo/1.0/backlog
Type: POST
Status: 500
Data: {
	"planId": <ID>,
	"scenarioId": <ID>,
	"filter": {
		"includeCompleted": true,
		"includeCompletedSince": EpochTimestamp,
		"includeIssueLinks": true,
		"performDependencyCompletion": false
	}
}

If the above doesn't match, check the Developer Tools > Network tab in your browser when loading the page and check the server response duration in the Timing tab:

Request URL: https://sitename.atlassian.net/rest/jpo/1.0/backlog
Request Method: POST
Status Code: 500 
Waiting for server response: 31.36s


Cause

A filter in use on the Advanced Roadmaps Plan is referencing an Issue Type that is no longer available on the Jira site. Also, the Issue sources in use on the Plan cover too many issues and are timing out when being accessed for display on the Plan.

Solution

Issue Type no longer exists:

  1. Navigate to the Advanced Roadmaps Plan
  2. Click the three dots menu > Configure, then click on Issue sources
  3. Find any filters in the list, then locate the same filter(s) under the View all filters list (sitename.atlassian.net/jira/filters)
  4. Confirm the JQL is referencing issue types that are currently present in the Jira site, and remove any unavailable issue types

Issue Source is timing out:

  1. Navigate to the Advanced Roadmaps Plan
  2. Click the three dots menu > Configure, then click on Issue sources
  3. Review the JQL configuration for the configured sources to identify any entries that might contain a complex query (usually signified by the OR clause) or return a very large number of issues
  4. Adjust the JQL configurations as necessary to limit the scope of the searched projects/issues

Additional Information:

Last modified on Feb 9, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.