Troubleshoot warnings on your timeline in your plan

As you schedule work for your teams, your plan warns you of any scheduling errors which are referred to as off-track dependencies. This page discusses common causes of warnings and how to resolve them.

Child issue starts before parent issue (or ends after)

If your plan is set to roll up dates, the parent issue automatically updates. But if you don’t, and you manually set dates for child issues which don't align with the dates of their parent, your plan generates a warning to highlight the conflict. This also applies when using sprint dates to schedule issues.

To resolve this:

• reschedule child issues so they occur within the dates of the parent

• change the dates of the parent issue to reflect that of the child issue or

• roll-up dates in your plan

Issue starts or ends after its due date

When scheduling issues, your plan uses the Due date field by default, though you can change which dates your plan uses to schedule issues. If an issue source in your plan uses a different date field, and you then schedule an issue to end after the date in that field, you’ll see this warning to alert you of the conflicting date fields.

To resolve this:

• add a column to your plan to show the date field configured on your issues

• open the issue view and change the date field on the issue directly

• reschedule issue on your plan to align with the date in the second date field

Open issue has passed its inferred/assigned end date

This warning tells you that you have open issues that are past their due date in your plan. The only difference between these two warnings is that one refers to issues using inferred rolled-up dates, and the other refers to those using manually set dates.

To resolve this:

• change the issue status to DONE

• move the issue to a different sprint

• change the issue’s end date

Issue scheduled outside of its assigned sprint

You’ll only see this warning if you have

• issues with a sprint assignment and manually set dates, and

• those dates fall outside the dates of the assigned sprint

To resolve this:

• move the issue to a different sprint

• change the issue’s dates to align with the sprint

Kanban issue assigned to a sprint

Sprints are only used by teams that plan work using the Scrum method of work planning. So you’ll see this warning if you assign an issue from a Kanban board to a sprint.

To resolve this:

• remove any sprint assignment from Kanban issues