Reorder and plan sequentially

Organize your timeline to show the work sequence and identify critical paths.

Reorder issues on the timeline

1. On the Timeline, locate an issue row
2. Drag the row up or down
3. Release the mouse

The issue position updates, and the timeline reflects the new order.

Use positioning to represent sequence

While the timeline’s horizontal position (dates) represents when work happens, the vertical position represents priority or sequence within a phase.

Drag higher-priority or earlier issues toward the top.

Plan sequential releases

1. Set Start Date and Due Date for each issue
2. Arrange issues so that dependencies complete before dependents begin
3. Use the timeline to visually confirm the sequence

For example:

• “Backend API” (Week 1–2)
• “Frontend integration” (Week 3–4) — depends on backend
• “Testing & QA” (Week 4–5) — depends on both

Set realistic timelines

When planning sequences:

1. Avoid overlapping deadlines for dependent work
2. Leave buffer time for testing and fixes
3. Account for team capacity and other commitments

Export or share timeline

Many teams take screenshots of the timeline for presentations or reports. The timeline visualization helps stakeholders understand the roadmap.