I have a filter that shows 2492 entries, but my roadmap is only showing 2370 issues and I am trying to figure out. I am not able to see why I am filtering out these 122 entries.
I have checked to make sure that I am not excluding releases, I have set the time filter to well before we started this project (3000 days).
Please advise where else I can look for filters that might be causing the issue
Hello @Michael A Paluszkiewicz
Welcome to the Atlassian community!
Have you gone through all the troubleshooting steps for missing issues, as listed here:
Hi Michael - Welcome to the Atlassian Community!
If your source filter returns 2,492 work items but the Plan only shows 2,370, I would check the Plan scope rather than the JQL first. In Jira Plans, items can belong to the source filter and still be excluded or hidden by Plan-specific rules. Atlassian provides a built-in way to diagnose exactly this.
The quickest test is to take the key of one of the missing items and search for the full work item key in:
Plan settings → Work in your plan
Jira should tell you whether that item is:
included in the Plan scope;
removed by a rule or manually;
or included but currently hidden by a timeline filter.
I would also check Plan settings → Work in your plan → Removed work items. Plans can exclude items based on things such as:
work type;
status;
release;
how long ago the item moved to Done;
or individual items that were manually removed.
Since you already increased the date window and checked releases, another area worth checking is the Hierarchy filter. If the missing 122 items belong to a hierarchy level that isn’t currently displayed, they may be in scope but not visible on the timeline. The Show full hierarchy option can also change what is displayed when filters are applied.
One additional check for completed items: Jira Plans can behave unexpectedly when an item is in a Done status but its Resolution/Resolved date was not populated correctly by the workflow. Atlassian lists resolution configuration as one of the common reasons for missing items.
So I would start with one known missing issue key rather than comparing all 122 at once. Once Jira tells you why that one is excluded, there is a good chance the remaining missing items share the same condition.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.