Create Recurring Issues in Linear
Use the recurring-issue action to create separate issues on a schedule. Editing the original template later does not update an already configured recurring issue.
Step-by-step guide
Check access and scope
Choose the team timezone and the person responsible for the repeated work. Recurrence is useful for a repeated task, not for hiding unresolved work.
Write the repeat checklist
Draft the repeatable issue with a clear completion checklist.
Choose recurrence
Use Make recurring in the composer or convert an existing issue. The composer menu offers Make recurring; an existing issue offers Convert into > Recurring issue.
- Worked example: A monthly access review should include a current member export, an exception check and a dated signoff. Each occurrence needs its own evidence rather than reopening one old issue.
Set cadence and date
Choose the first due date and repeat cadence.
Review team recurrence settings
Review the recurring entry in team settings.
Inspect the first occurrence
Inspect the first generated issue and adjust the recurring definition itself. The documented generation behavior follows the due date at 00:01 the next day in the team timezone.
Verify the result
The recurrence entry shows the expected cadence and a generated issue contains the intended current checklist.
Common mistakes
Avoid the main failure mode
Expecting the next issue exactly at the start of its due day is misleading; documented generation follows the due date in the team timezone.
Check the handoff edge case
Putting an individual name in a permanent recurring checklist without a replacement process leaves generated issues assigned to departed owners.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.