How to Fix Linear Cycle Planning Issues Not Appearing

In this tutorial, you'll learn about How to Fix Linear Cycle Planning Issues Not Appearing. We cover key concepts, practical examples, and best practices.

Linear cycles group work into time-boxed periods (like sprints). When issues do not appear in cycle planning, the issues were not assigned to the cycle, the cycle is closed, or the team's view filters exclude them.

The Problem

You open the Cycle view and expected issues are missing. The cycle shows fewer issues than the team planned. New issues are not appearing as expected.

Wrong approach — recreating the cycle.

The Fix

Check if issues are assigned to the cycle:

1. Open the issue
2. Check the "Cycle" field in the issue detail panel
3. If it says "No cycle," the issue is not in any cycle
4. Click the cycle field and select the correct cycle

If the cycle is closed (past date range):

1. Closed cycles are read-only
2. Issues in closed cycles still show in the cycle's history
3. To add work, open a current or future cycle
4. Future cycles are visible in "Upcoming" view

Check the view filters in cycle planning:

1. In Cycle view, check if any filters are active (top of the view)
2. Filters like "Only my issues" or "Label = Bug" may hide issues
3. Clear all filters to see all issues in the cycle
4. Use "All issues" view to verify issue assignment

Expected output:

Cycle shows all issues assigned to that time period
New issues can be added to current and future cycles
Cycle view accurately reflects the team's planned work

Prevention Tips

• Assign issues to cycles when creating or planning them
• Use "Upcoming" cycles to plan future work in advance
• Review the cycle view at the start of each cycle to verify all planned issues are present
• Use the "Cycle" column in list view to see which issues are missing cycle assignments
• Archive completed cycles to keep the view focused on current work

Common Mistakes with cycle planning

1. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
2. Using head and tail instead of pattern matching, causing runtime errors on empty lists
3. Forgetting that lazy evaluation defers computation until the value is forced, causing space leaks with unevaluated thunks

These mistakes appear frequently in real-world LINEAR code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Related: DodaTech's Cycle Velocity Tracker measures story points completed per cycle, team capacity trends, and cycle completion rates to improve planning accuracy. Use with DodaZIP for backup.