Auto-Archive GitHub Project Items
Use a project auto-archive workflow with a conservative completion-and-age filter. Archiving removes project clutter while retaining project field data, but affects Insights coverage.
Step-by-step guide
Check access and scope
You need workflow management access. Review all currently matching items because enabling auto-archive can archive existing matches as well as future ones.
Define retention scope
Choose the completed work and inactivity window appropriate for review.
Preview existing matches
Preview the intended scope using project filters.
- Worked example: A filter such as is:closed reason:completed updated:<@today-14d can target older completed issues. The two-week window is an example; choose a retention window that fits your review process.
Open auto-archive
Open Auto-archive items in project Workflows. Open Workflows and select Auto-archive items, then review the criteria before choosing Save and turn on workflow.
Set supported criteria
Configure supported is, reason and updated criteria.
Inspect archived samples
Enable the workflow and inspect archived samples.
Verify the result
Matching items leave active views and retain expected field data in the archive.
Common mistakes
Check the handoff edge case
Archiving existing matches immediately can change reporting coverage. Review the matching set before enabling the workflow.
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.