Repository navigation
v0.7.0
Everything a team moving from another tracker needs on its first day: dates and estimates,
sub-issues and relations, Markdown with attached files, filters and saved views, calendar, table
and timeline layouts, and imports from CSV, GitHub and Linear. Updating a self-hosted copy applies
migrations in each workspace's database, which run on their own; there is no D1 migration this
time. Attached files need R2: turn it on in the Cloudflare dashboard before updating, and
pnpm run deploy creates the bucket, or delete the r2_buckets lines from wrangler.jsonc to
run without attachments. (#68, #69)
Added
- Start dates, due dates and estimates in points on issues. Lists and boards show the due date,
in red once an open issue is overdue, and the issue page sets them (D and E). MCP's
create_issueandupdate_issuetakestart_date,due_dateandestimate. (#63) - Sub-issues: an issue can have a parent in any team, shown above its title, and lists its
sub-issues with their progress under the description. Deleting a parent keeps its sub-issues as
top-level issues. MCP takes and returnsparent, andget_issuereturnssubIssues. (#64) - Relations between issues in any teams: blocks, duplicate of and related. The issue page lists
them by kind, lists and boards mark a blocked issue, and an open duplicate offers "Close as
duplicate". MCP haslink_issuesandunlink_issues. Relations send no webhook events yet.
(#66) - Descriptions and comments are GitHub-flavored Markdown, and files of up to 25 MB can be pasted,
dropped or picked into them. Files are kept in R2 and served only to members of the workspace.
Images from other sites show as links, so opening an issue tells no one who read it. (#68) - Three more layouts for pages of issues: a calendar by due date, where dragging an issue to a day
sets its due date (#67); a table with a column per property, editing in place, sorting and a
choice of columns (#73); and a timeline from start to due date, where dragging a bar moves its
dates (#74). - One Filter menu for status, priority, assignee, project, labels, team and due date. The filters
in force show as chips and live in the URL, and an issue created on a filtered page takes them,
so it shows up there. (#75) - Saved views: filters and a layout under a name in the sidebar, shared with the workspace or
personal. Changes on a view's page are saved into it or as a new view. Personal views are hidden
from others in the app but, like everything in a workspace, are in each member's local copy.
(#76) - Import issues in Settings > Import from a CSV file (Track's own export, or another tracker's by
common column names), from GitHub Issues or from Linear, with their original creation dates. A
GitHub token or Linear key goes from the browser to GitHub or Linear only. Running an import
again skips what it already brought in. (#70, #71) - Export a workspace or one team as CSV or JSON, in Settings > Export or from the command palette.
(#65) - A new workspace starts with a team and a few issues that show you around, unless that box is
unticked, and an empty workspace offers the same. (#61) - MCP:
create_projectandupdate_project. (#62)