nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Isse with solved Status are not shown in Roadmap

Ming Xia_oekmcf

hallo,

i have one question to advanced Roadmap. if I switch the issue status to resolved, then the issues (epic, Story, Task and so on) will be not display in the roadmap. It leads problem in Review of the issue in past.

how can I change the setting so that the issues with Status Resolved also show in the roadmap.

thanks a lot

Accepted answers

James Gamble

Hola Ming,

This is usually controlled by the plan settings or by the issue source behind the plan, not only by the status itself.

Advanced Roadmaps can hide completed work after a certain number of days. By default, completed issues are excluded after 30 days. If you want resolved items to remain visible for review, check the plan’s exclusion settings.

In the plan, go to Plan settings > Exclusion rules, and look for the setting that excludes completed issues after a specified number of days. Increase that number to the period you want to review.

Atlassian documents that behavior here: https://support.atlassian.com/jira-software-cloud/docs/how-advanced-roadmaps-handles-completed-and-resolved-issues/

I’d also check the source of the issue for the plan. If the plan is based on a board, project, or saved filter, ensure the source does not exclude resolved work. For example, a filter with something like this would remove resolved items before Advanced Roadmaps ever gets them:

resolution IS EMPTY
or:
statusCategory != Done

One more thing to check is the Resolution field. Jira and Advanced Roadmaps treat completed/resolved work based on the Resolution field, not just the status name. If your workflow moves an issue to a “Resolved” or “Done” status but does not set the Resolution field, Advanced Roadmaps may not treat it correctly.

Thanks,

James

All comments

James Gamble

Hola Ming,

This is usually controlled by the plan settings or by the issue source behind the plan, not only by the status itself.

In the plan, go to Plan settings > Exclusion rules, and look for the setting that excludes completed issues after a specified number of days. Increase that number to the period you want to review.

Atlassian documents that behavior here: https://support.atlassian.com/jira-software-cloud/docs/how-advanced-roadmaps-handles-completed-and-resolved-issues/

resolution IS EMPTY
or:
statusCategory != Done

Thanks,

James

Ming Xia_oekmcf

Hi James,

thank you for the reply and suggestion. I will try and check the settings

BR and have a nice weekend

Ming

Ming Xia_oekmcf

I have checked the Exclusion rules. it looks correct. I will check another field

James Gamble

Hola Ming,

Thanks for the screenshot.

One thing stands out: your exclusion rules also exclude the CLOSED work status. If the issues move from Resolved to Closed, or if your workflow treats Closed as the completed status, that could explain why they disappear from the plan even though the 30-day setting looks correct.

I’d try removing “CLOSED” from “Select work status to exclude,” then refresh the plan. If the issues appear again, then the exclusion is coming from that status filter rather than the number of days.

If they still don’t show, I’d check the plan source next. If the plan is based on a board or saved filter, make sure the source filter doesn’t exclude resolved or closed issues by using criteria such as resolution IS EMPTY, status != Resolved, or statusCategory != Done.

Thanks,

James

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud