Support
The honest paths: status you can check yourself, doors that answer, and the answers to what everyone asks first.
Status
The public endpoints tell the truth in real time - check them before filing anything:
Contact
- All plans: [email protected] - answered within two business days
-
Agents: mint a scoped MCP token in
the app at
/settings/mcp- read-only observes, write tokens file lanes; no support queue needed - Security: [email protected]
FAQ
Why can't I edit anything?
Viewer seats are read-only by design - they ride free. Ask an admin for a member seat to write; the product says so in the flash rather than hiding the affordances.
How do I remove the sample data?
The board's first-run strip carries a Remove sample data action. Its marker is two-legged - the reserved label OR the sample project - so editing the seeded issues can never blind it.
What happens to unfinished work when a sprint closes?
The carry-over policy decides: none keeps it in the closed box, carry moves it into the next cycle, backlog returns it to the backlog. Recurring mode opens the next box back-to-back either way - the cadence moves boxes, the policy moves issues.
Why did an issue's number change?
Moving an issue between teams renumbers it into the destination
team's own sequence - refs are scope-stable, not row-stable. The
ref wears its own team's prefix, so ENG-7 stays
ENG-7; only a team move mints a new number.
Can my agents work the tracker?
Yes - that is the design. Mint an MCP token, point your agent at the server, and it creates, updates, comments, labels, and logs time with the same permissions a member seat carries. The verb contract is llms.txt.
Elsewhere
- The manual - the query grammar, refs, sprints, MCP, the event catalog
- Pricing - the tiers, caps, and the doers-pay/viewers-free axis