Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
As you schedule work for your teams, Advanced Roadmaps will warn you if there are any misaligned dates in your plan. This page discusses common causes of warnings, and how to resolve them.
Starts before parent
If you set dates for issues that don't align with the dates of their parent, Advanced Roadmaps will generate a warning highlighting the conflict, as shown below:
To resolve this, adjust your dates so that the child issues fall within those of the parent. This also applies when using sprint dates in the plan.
Target dates set beyond the due date
Depending on how your plan is configured, your plan view may also show Due dates that Advanced Roadmaps imports from Jira Software. If you set a target end date that extends beyond the assigned due date, Advanced Roadmaps will generate a warning, as shown below:
To resolve this, adjust the target end date or the due date.
Unresolved issue after target end date
Advanced Roadmaps will warn you when an issue in your timeline has already passed its end date.
To resolve this, update the status of the issue or its end date. If the unresolved issue is in progress, you'll be prompted to do one of the following:
Move the issue status back to TO DO
Add the issue to a different sprint
Reschedule the issue to a later end date
Was this helpful?