Troubleshoot Missing Issues in Advanced Roadmaps for Jira Data Center

Summary

Some Jira issues don't appear in the Advanced Roadmaps for Jira plans. You have checked our documentation and are sure the issue should qualify for it.

Environment

Jira Software Data Center 8.15 or later, with the Advanced Roadmaps app installed.

Solution

There could be multiple reasons for issues not appearing in plans. Before going through the list below, please ensure that you have checked our documentation. Then, check the list below to see if any of the listed use cases apply to your situation.

• 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 out some of the issues. Make sure your hierarchy filters include the range of issue types to which a missing issue belongs

• If the missing issue is a sub-task, check if the parent of the sub-task is excluded by the plan hierarchy filter:

  • Open the subtask and note the type of its parent issue (for example, Story, Epic, etc.).

  • 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

• The issue might be associated with an archived release. These are not included in the plans, but you may unarchive the release and remove the issue from it if needed

• 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 the Issue Sources configuration and make sure that the "Completed issues" parameter is set to the interval that covers the missing issue

• Parent issues, such as Epics, will not appear if all their children are closed without a resolution being set

• Some issues might be in a resolved status (=status which is of the "Done" category as per its configuration in ⚙ > Issues > Statuses), but don't have a Resolution set, or have a Resolution set without a Resolution date (which normally appears in the Resolved field of the Dates panel)

  • Those issues will be hidden from the plan

  • For more information about this scenario, please refer to the article Missing Done Issues in Advanced Roadmaps Plan - Jira Data Center

• The issue source might be using a filter that contains multiple filters. In this scenario, you need to have Read access to all the filters individually

• The missing issues might be archived (archived issues are not shown in Plans)

  • To verify if it is the case, open the issue from the Issue View page (by using the direct link of the issue) and check if it is showing as archived

• Check if the View Settings > Group by option is set to Release, as an empty Release field can affect the visibility of the issue:

  • If that's the case, the following will happen:

    • If the Fix Version/s field is empty for a child issue but not for its parent issue, the issue will be hidden from the Plan

    • This behavior not only impacts sub-tasks, but it can also impact Stories

    • You can find below a few scenarios where a "child" issue will be missing from the plan:

      • Scenario 1

        • Let's assume that an Epic issue has a Story issue underneath it, and that the Epic has a Fix Version but not the story

        • In this case, the Story issue will be hidden from the Plan

      • Scenario 2

        • Let's assume that a Story issue has a Sub-task issue underneath it, and that the Story has a Fix Version but not the Sub-task

        • In this case, the Sub-task issue will be hidden from the Plan

  • To check if an issue is missing because of this option:

    • Check if the missing issues appear in the plan when changing this option to None

    • If the missing issues appear, open the issue in the "View Issue Page", and check the Fix Version/s field

    • If this field is empty, then it explains why the issue was hidden from the Plan: if the group by option is set to Release, the issue needs to be added to a release to show in the Plan

• 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

• 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 - Unable to fetch Child Issues when multiple Parent Link custom fields are in use

• 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. See also Some issue types are missing from an Advanced Roadmaps Plan, and JSWSERVER-24898 - Issues in projects with hidden fix version field are not imported into Portfolio plans

• If only child issues are missing from a Plan, they might be missing because of the issue described in The Dark Theme Mode is not supported by Advanced Roadmaps for Jira. Basically, if Jira is on any version from 10.3.0 and below 10.7.0, child issues will be missing from any Plan if the Dark Theme is used. In such a case, we recommend using the Light mode instead of upgrading Jira to the fixed version.

• Check your Jira application logs for error messages like

  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

• If all the above steps don't match or their solutions did not fix the problem, we may have corrupted plan index data for the plan scenario, detailed in the bug JSWSERVER-25296 - As a Jira user I would like to fix corrupted ARJ Plan indexes when they get corrupted.  A simple validation and workaround is to create a new scenario as a copy of the problematic scenario.  Check if the missing issues are found in the new scenario.  If found and further testing indicates the new scenario contains correct data, then we can delete the old scenario and rename the new scenario with the old scenario's name.

• Try to create a new alternate Plan connected to the same project or boards and compare the results

• If the issue is not reproducible in a new Plan using the same configuration, it would be possible to refresh the Plan cache by clicking on 'Auto-Schedule' > Preview Results, but canceling the action afterward