Skip to content

Database governance built for humans and agents — controlling changes and access across every major database.

docs(agents): file agent-created Linear issues in team BYT (#21684)

zchpeterf088be76d2b5
diff --git a/.claude/skills/e2e-routine/SKILL.md b/.claude/skills/e2e-routine/SKILL.md
index 9a62dab570..8d4509d3d9 100644
--- a/.claude/skills/e2e-routine/SKILL.md
+++ b/.claude/skills/e2e-routine/SKILL.md
@@ -34,9 +34,9 @@ issue body is `references/issue-template.md`; the ledger format is
- **Processes**: never kill a process you did not start. The harness owns its
server (PID file, port 18234 with fallback). A port conflict is reported, not
resolved by killing.
-- **Linear**: the team in `E2E_ROUTINE_LINEAR_TEAM` only (default `BOT`, the
- agent-issue team from docs/agents/issue-tracker.md), parent = the issue in
- `E2E_ROUTINE_UMBRELLA`.
+- **Linear**: the team in `E2E_ROUTINE_LINEAR_TEAM` only (default `BOT`). The
+ routine's owner names this team, which docs/agents/issue-tracker.md allows in
+ place of `BYT`; parent = the issue in `E2E_ROUTINE_UMBRELLA`.
Create issues and comments only when `E2E_ROUTINE_FILE_ISSUES=1`; otherwise
write proposals into the report. Never edit, retitle, close, reassign or
relabel an existing issue: a comment and its evidence attachments are the
diff --git a/AGENTS.md b/AGENTS.md
index afec0fb795..198a1351d1 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -12,7 +12,7 @@ Bytebase is the standard for database development. Every product and engineering
- For frontend work, read [frontend/AGENTS.md](frontend/AGENTS.md); before changing UI, also read the [UX contract](docs/agents/frontend-ux.md).
- Before adding or modifying metadata SQL, pagination, or multi-row transactions anywhere in the repo, read [backend/store/AGENTS.md](backend/store/AGENTS.md). This includes CEL-to-SQL filters and raw reads in tests.
- Before changing metadata/DDL conversions or their golden fixtures, read [backend/plugin/schema/AGENTS.md](backend/plugin/schema/AGENTS.md). It covers what these packages test and the `record` process for regenerating fixtures.
-- For issue operations, read [issue-tracker.md](docs/agents/issue-tracker.md). Linear is the tracker; agent-created issues go to team `BOT`. For triage, also read [triage-labels.md](docs/agents/triage-labels.md).
+- For issue operations, read [issue-tracker.md](docs/agents/issue-tracker.md). Linear is the tracker. For triage, also read [triage-labels.md](docs/agents/triage-labels.md).
- Before creating a PR, complete [docs/pre-pr-checklist.md](docs/pre-pr-checklist.md).
- `AGENTS.md` files are the instruction source of truth; `CLAUDE.md` files import them.
diff --git a/docs/agents/issue-tracker.md b/docs/agents/issue-tracker.md
index ac8c9c60b5..7800923f76 100644
--- a/docs/agents/issue-tracker.md
+++ b/docs/agents/issue-tracker.md
@@ -4,21 +4,19 @@ Issues and PRDs for this repo live in Linear. Linear is the source of truth for
Use Linear MCP for Linear operations when available; otherwise use `linctl`. The repo is GitHub-hosted for code review and implementation history: GitHub PRs should reference or attach to the relevant Linear issue, but GitHub Issues and GitHub PRs are not treated as the request tracker or triage queue.
-## Agent-created issue isolation
+## Target team
-Agent-created issues must go to Linear team `BOT`, not the main product backlog. This keeps exploratory triage, generated PRDs, and wayfinding tickets out of the team's normal planning queue.
-
-Only create or move issues into a product Linear team when the user explicitly names that team and asks to publish there. Otherwise, publish new issues to team `BOT` and leave promotion to a product team as a human decision.
+Product issues go to Linear team `BYT` (Bytebase). File in another team only when the user names it.
## Conventions
Prefer Linear MCP tools for create/read/update/comment operations when the session exposes them. If Linear MCP is unavailable, use these `linctl` commands:
-- **Check the target team**: `linctl team get BOT`.
-- **Create an issue**: `linctl issue create --team BOT --title "..." --description "..." --labels needs-triage`.
+- **Check the target team**: `linctl team get BYT`.
+- **Create an issue**: `linctl issue create --team BYT --title "..." --description "..." --labels needs-triage`.
- **Read an issue**: `linctl issue get <issue-key>`.
-- **List issues**: `linctl issue list --team BOT` and filter by triage label/status using the mappings in `triage-labels.md`.
-- **Search issues**: `linctl issue search "<query>" --team BOT`.
+- **List issues**: `linctl issue list --team BYT` and filter by triage label/status using the mappings in `triage-labels.md`.
+- **Search issues**: `linctl issue search "<query>" --team BYT`.
- **Comment on an issue**: `linctl comment create <issue-key> --body "..."`.
- **Apply / remove triage labels**: use `linctl issue update <issue-key> --labels ...`. `linctl issue update --labels` replaces labels, so fetch the current issue first and pass the full intended label set.
- **Close**: `linctl issue update <issue-key> --state "Done"` or the appropriate canceled/won't-fix workflow state, and leave a closing comment when context is needed.
@@ -30,7 +28,7 @@ GitHub PRs are **not** a request surface for triage. They may link to Linear iss
## When a skill says "publish to the issue tracker"
-Create a Linear issue in team `BOT` using Linear MCP or `linctl` unless the user explicitly names a product Linear team and asks to publish there.
+Create a Linear issue in the target team using Linear MCP or `linctl`.
## When a skill says "fetch the relevant ticket"
@@ -38,10 +36,10 @@ Fetch the Linear issue referenced by the user, normally by Linear issue key or U
## Wayfinding operations
-Used by `/wayfinder`. The **map** is a Linear issue in team `BOT` with child Linear issues as tickets.
+Used by `/wayfinder`. The **map** is a Linear issue in the target team with child Linear issues as tickets.
- **Map**: a single Linear issue holding the Notes / Decisions-so-far / Fog body. Label it with the tracker equivalent of `wayfinder:map` if that label exists; otherwise use the issue title or description to identify it as the map.
-- **Child ticket**: a Linear issue in team `BOT`. Record ticket type in a label or description field: `research`, `prototype`, `grilling`, or `task`. Link the child to the map with `linctl issue update <child-key> --parent <map-key>` when Linear parent relationships fit.
+- **Child ticket**: a Linear issue in the map's team. Record ticket type in a label or description field: `research`, `prototype`, `grilling`, or `task`. Link the child to the map with `linctl issue update <child-key> --parent <map-key>` when Linear parent relationships fit.
- **Blocking**: use Linear issue relations: `linctl issue relation add <child-key> --blocked-by <blocker-key>`. List blockers with `linctl issue relation list <child-key>`.
- **Frontier query**: list open child tickets for the map, drop claimed or blocked tickets, and choose the first remaining ticket in map order.
- **Claim**: assign the Linear issue before starting work: `linctl issue assign <issue-key>` or `linctl issue update <issue-key> --assignee me`.