Using a filter as the source for a plan loses the dates and ticket linking

[Trevor Raiss]

I have a project which spans multiple teams, some are kanban and some are scrum. Their tickets are grouped under Epics within their teams, and I have created an Initiative to group all the Epics across the teams. I want this Initiative to show in a Jira Plan.

I created a filter which shows everything in the Initiative using issuekey in portfolioChildIssuesOf("RIS-1514") which when I view this filter, it lists all the expected tickets. 

When I create a plan and set this filter as the source, the Plan Timeline shows all the expected tickets, but for tickets in a scrum project, it doesn't show dates (which should be inferred from the sprint dates) and doesn't show links to other tickets. If I change the source of the Plan to be one of the teams boards (which itself contains multiple projects, and are all scrum projects), the dates and links are displayed correctly.

Besides changing the source, all other settings are default. Estimation = Days, Dates = Start Date and Due Date, Inferred Dates = Sprint dates. 

Why would the use of a filter as the plan source prevent the dates and links showing up for scrum projects?

[Walter Buggenhout]

Hi @Trevor Raiss ,

To infer the dates from sprints, the sprints themselves should be in your plan. As sprints are created as part of a board, the board is needed in Advanced Roadmaps to map out these planning features.

It's as simple as that, basically. It is very much recommended to use boards as issue sources to your plan instead of filters or projects, because that unlocks quite a few additional planning features that become unavailable otherwise.

Hope this helps!