Sprint start/end dates are not synced with start and due date fields in an Advanced Roadmaps plan even if inferred dates is set as "Sprint dates"
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
From the advanced roadmap plan settings (Configure > Scheduling), we have the option to set the inferred dates as the Sprint dates. This should ensure that the start and due dates for the issues in the advanced roadmap plan are seen as sprint dates with "S" prefixed.
However, in certain cases, we notice that the Sprint start and end dates are not synced in the plan.
Environment
Jira cloud (Advanced Roadmaps)
Cause
The Advanced Roadmap plan's issue source is a filter or non-scrum board and hence the sprint dates are not seen despite inferred dates set to "Sprint dates"
Solution
Ensure that the plan's issue source is a scrum board that uses sprints as "Sprint dates" can be used if the issue source is a scrum board with sprints.
Reference documentation: Schedule issues in Advanced Roadmaps according to sprints