Problem

Some Jira issues do not appear in the Advanced Roadmaps for Jira plans. You checked the issue sources in the plan and are sure the issue should qualify for it.

Cause

There could be multiple reasons for issues to not appear in plans. Please check the list below to see if any of the listed use cases apply to your situation.

• The issues might be removed from the Issue Source by checking in the Removed Issues feature.
• Your plan view might have filters applied. Make sure that the issue does not appear with all filters removed before proceeding further.
• Your plan hierarchy filters might filter some of the issues out. Make sure your hierarchy filters include the range of issue types a missing issue belongs to.
• If the missing issue is a sub-task, check the points below:
  • Open the sub-task and take note of the type of its parent issue (for example: Story, Epic...)
  • Open the plan the sub-task issue is missing from
  • Check the hierarchy levels that are currently selected
  • If the selected hierarchy levels exclude the parent issue of the sub-task, then the sub-task will not show in the plan
  • For example:
    • Let's assume that the sub-task is a child of an Epic type issue
    • In such case, if the selected hierarchy levels are "Story to Sub-Task", then the sub-task will not show since its parent is an Epic and the Epic level is excluded from the plan
    • To show the sub-task, you will need to make sure that the selected hierarchy levels are "Epic to Sub-Task"
• Issues might be filtered out because of the Release settings of the Issue Sources. Confirm that the issue does not belong to releases that are being filtered out in Issue Sources settings.
• Issue might be associated with an archived release. These are not included in plans but you may unarchive the release and remove the issue from it if needed.
• Issues might be filtered out because of the Scope settings of the Issue Sources. Confirm that the issue is in the result of a JQL search using the filter/board filter query.
• Issues in completed status might be filtered out of a plan if they were resolved prior to the configured cutoff threshold in the issue sources. Check Issue Sources configuration and make sure that "Completed issues" parameter is set to the interval that covers the missing issue.
• Issues in a completed status but without a Resolution set will not show up in plans Closed issues do not show up in Advanced Roadmap Plans.

• Some issues might be in a resolved status, but do not have a resolution date for whatever reason. Those issues will be filtered out of the plan regardless of a cutoff setting in the Issue Sources configuration. Check if your issue qualifies for the following JQL:  Some issues marked as Done are missing from an Advanced Roadmaps plan

  statusCategory = done AND resolutiondate is null

  Issues must have a valid resolution date set in order to be included in the plan. Further investigation is needed to find the cause. Contact Support with the results of the query, to be able to fix the issue and prevent further issues.

• The issues are scheduled outside the Plan's selected scope. You may try selecting "1Y", "Fit" or a custom time range that encompasses the missing issues schedule.
• The field "Fix Version/s" is hidden in the Projects' Field Configuration. If that's the case, you need to show the field in all Field Configurations in use by the Projects imported into the Plans and reindex Jira for the changes to take effect. This may affect specific issue types since the Field Configuration is not necessarily the same for the entire project: Some issue types are missing from Advanced Roadmaps plan
  • Please refer to JSWSERVER-24898 - Getting issue details... STATUS
• There are multiple "Parent Link" type custom fields in Jira and the "Child issues" panel may not even be visible for some users
  • Please refer to JSWSERVER-24810 - Getting issue details... STATUS
• Try to create a new alternate Plan connected to the same project or boards and compare the results.

• When checking Jira application logs you notice the following error message: 

  2023-04-04 11:50:07,099+0200 https-jsse-nio-8443-exec-2890 url: /rest/jpo/1.0/issues/rank; user: xxxx WARN xxxxx 710x166898842x4 xx xx /rest/jpo/1.0/issues/rank [c.a.r.j.i.l.issue.scenario.DefaultScenarioIndexService] Received out-of-sync scenario issue changed event; change event has sequence '1918', cached sequence is '1916'. Invalidating cache. Full index rebuild will occur on next request.

  • Run Integrity Checker and Full Reindexing to fix the plan index cache out-of-sync issue.