Repository navigation
v0.15.0
Closed issues can be archived out of lists and boards. Updating a self-hosted copy applies a
migration in each workspace's database, which runs on its own; there is no D1 migration and no
new setting. The protocol goes to version 17, so open tabs reload and sync again. (#105)
Added
- Archive a completed or canceled issue from its page, and it leaves the lists and boards of its
team, project, cycle and saved views, and My issues. Search, its page, its history and the
progress of its project, cycle and parent keep it. (#105) - Each team has an archive page, linked from the team page once something is in it and from the
command palette, where archived issues can be restored. Reopening an archived issue restores
it too. (#105) - Over MCP,
search_issuestakesarchived, every issue says whether it is archived, and
update_issuearchives or restores an issue. Webhooks send it asissue.updated, with
archivedAt. (#105)