Filter resuls not showing up in Advanced Roadmap Plan

Question

Using advanced Roadmaps, I noticed that some of my epics are not showing up in the plans I create. After some experimentation I found that this applies to all Epics in a Released state in a specific project. Other projects and states dont seem to have the problem.

I can see the problem by creating a simple query to list all epics in that state in that project (lets say that gives 300 results). However when I create a plan using only that filter, even while still in the "issue source" screen, it shows me that the filter does not produce any results. If I change my filter to use one of my other projects, I dont see the problem.

I thought maybe it was something to do with resolution states not being set correctly in that project so I updated those to ensure they were consistant with other projects but that has not fixed the problem.

I've also gone through all the Atlassian steps for checking for missing results (eg issue age, issue exclusion, etc) and none apply in this case.

Has anyone encountered this problem before and if so any ideas on what magic I need to do to fix it?

Niharika Sarabu · Answer

I am writing here, if any others with similar problem might be coming here with same problem.

The reason of missing tickets from a filter source ( which are available/visible in filter results) in a plan would be :

The "Status Category" ( like TO DO , In Progress, Done) mapped to those statuses of the respective tickets.
If a ticket is in status "Ready For Delivery" with category of this status is mapped to "Done" (normally displays in green), then that ticket is not displayed in the plan from that filter but visible from project source ( sounds weird ) but this is how it is working.

So we will need to be careful while creating a new status with status category.

Earl McCutcheon · Answer

Hi @rSloan ,

Thanks for the update, and you already noted checking the exclusion rules, but this really seems like a exclusion setting is being triggered.  you noted the Epics are marked as done, and also part of a release so both of these options have a potential to be tied to an exclusion rule.

Per the done status the default setting is to exclude all done statuses, at 0 days, but can be modified to certain statuses or longer periods, so this is leading me to think that the completed issues are set to be excluded and were completed prior to the day setting in the exclusion rule.

Can you grab a screenshot of the Exclusion rules under the plan settings but also Check the Plan settings under the  Exclusion Rules section, to see if the value for the field "Exclude any completed issues after"  is a number of days less than the resolution date on the missing epics.  Or if certain statuses are excluded.  Additional details on this setting can be seen in:

* https://confluence.atlassian.com/advancedroadmapscloud/issues-998651191.html#Issues-completedissues

Next, you mentioned that the epics are in a release that is marked as released, this may be another exclusion on the release,  and if this is the case there will be an indicator just below the "Exclude releases" option noting the number of releases excluded, clicking on this will give you the option to re-include the releases if this is the case.

Regards,
Earl

rSloan_jakgmj · Answer

We uncovered the answer via Atlassian support which I wanted to post here.  The offending epics which were not showing up were mapped into a release (fix version) which had been accidently archived. Apparently theere is a limiation on Advanced Roadmaps in not showing epics from archived releases.

Un-archiving the release fixed the issue.