Issues without start/end date in sprints that don't have a start/end date are estimated

Issues in a plan have sprint dates suggested by Advanced Roadmaps even if the sprint that the Jira issue is in is not yet started and has no start/end dates defined within the sprint.

This can give a false time range to the planner, given that the guessed dates are not differentiated to dates actually pulled from the sprint. The font is the same, and, they both indicate [S], suggesting the dates are inferred from the sprint dates, which they are not.

Suggested Solution

• Provide a configuration option to only suggest dates if the sprint has start/end dates or the issue has start/end dates
• Modify the rendering of the [S] label and suggested date font to indicate that the date did not come from the sprint, rather, was guessed based on other factors