Repository navigation
v0.8.0
Cycles: a team can work in fixed runs of one to four weeks, and Track moves them on by itself.
Also webhook events for relations, and importing Track's own JSON export. Updating a self-hosted
copy applies a migration in each workspace's database, which runs on its own; there is no D1
migration. The protocol goes to version 11, so open tabs reload and sync again. ([#82])
Added
- Cycles. An admin turns them on for a team, with a length of one to four weeks, the day the next
one starts and the time zone its days follow. The workspace keeps two cycles ahead, completes
each at midnight after its last day and moves its unfinished issues to the next one, as Track.
Issues are planned into a cycle from their page, the new-issue dialog or the table. A team's
cycles page lists the current, upcoming and completed ones with their progress, and each cycle
has a page with its dates, progress in issues and points, a burn-up and its issues. Filters and
saved views can follow the current or next cycle. MCP'sget_workspacelists open cycles, and
search_issues,create_issueandupdate_issuetakecycleas"current","next"or a
number. Webhook events for the moves Track makes carry an actor of typesystem. ([#82]) - Webhook events for relations:
relation.createdandrelation.deleted, with both issues and
the relation. New webhooks leave them off until chosen. ([#78]) - Settings, Import reads Track's own JSON export as well as CSV, so a workspace or a team can move
to another workspace, such as from a self-hosted copy to Gateweave Cloud. Issues keep their
comments, parents, labels, projects and relations, and the file's teams can be kept. Repeating
an import skips what is already there. ([#81])
Changed
- The JSON export includes cycles. ([#82])