Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why are closed issues that are resolved not included in the scope when creating a new plan?

I create a filter and the results include both open and closed issues linked to an epic. When I create a new plan the closed issues are not part of the scope in Step 3 of 3. Can't determine why they aren't being included.

2 answers

1 vote
Paul O Rising Star Mar 19, 2021

This is probably because plans default to not showing issues closed more than 30 days .  After you've built your plan, go back to the plan configuration -> Issue Sources  and change the completed issues setting. By default it's 30 days - increase the number to 90 or 180 etc than switch back to you plan and you should see closed issues that were part of your filter

0 votes
Dave Atlassian Team Mar 19, 2021

Hi @Eric Thompson,

As @Paul O says this is almost certainly due to the date that the issues were resolved on (however, if you are using a custom workflow that is not setting a resolution date then no resolved issues will be included because it is not possible to determine how recently the issue was resolved).

The reason that older resolved issues are excluded is because there is a limit on the number of issues that can be loaded into a plan. Generally speaking the more issues loaded the worse the performance will be. Advanced Roadmaps is considered a planning tool so the expectation is that users will be looking at future issues (as well as in progress and recently completed ones). If plans continued to load all resolved issues then plan load times would get slower and slower over time as more and more issues get loaded into the plan.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events