DRU-387 - Local issue tracker

[chaosk]

Linear ticket: DRU-387

A ticket tracker that lives in this appliance. Software Factory can use it instead of Linear or Jira. There is nothing to paste in Settings → Services. Selecting tracker issues (the select shows druks) is the whole connect.

This is Software Factory, not a second bundled app and not a Service card. There is no issues entry point and no alembic_version_issues.

What the operator gets

• Board /software_factory/board and list /software_factory/list. Overview stays the React home.
• Tickets {project.prefix}-{n} (for example BOX-3). Title, markdown description, status, priority, optional assignee, comments.
• Repo is a required field. Prefix and sequence live on the GitHub Project that repo sits in. Moving a ticket to another repo does not remint the identifier.
• Statuses: Backlog, Todo, Ready for Agent, In Progress, In Review, Done, Cancelled, Blocked. Default create is Todo. Ready for Agent is the build trigger.
• Ticket detail saves in place (title, description, sidebar). Sidebar names Created by, Created, and Updated. Board cards open the ticket; there is no separate Open control.
• Board cards drag onto a status column. The shell previews the landing column and commits that column on drop. Same-column drop does nothing. Status still goes through set_status.
• Description and comments edit as formatted markdown. The API still stores a markdown string.

How a build starts

ticket.transitioned still feeds Build.dispatch. The in-process IssuesTracker writes status back onto the ticket row. No webhook, no Service identity.

Ready for Agent opens a build against the selected repo. If that ticket already has a scheduled, running, or parked build, dispatch mirrors the ticket onto that run (In Review when parked on review, otherwise In Progress) instead of starting a second one.

When the tracker is issues, the sandbox also gets this appliance’s /mcp as druks, credentialed with a run PAT, so the agent fetches and comments with software_factory_get_ticket / software_factory_add_comment. Prompts treat a Druks identifier like Linear/Jira, not as a GitHub issue number.

Out of scope

Comment edit/delete, attachments, labels, estimates, Linear import, a standalone Issues app.

Tickets (all landed on integration/issues)

• DRU-388 — models, tables, identifiers
• DRU-389 — create / edit / comment / status doors
• DRU-390 — board, list, ticket pages
• DRU-391 — Software Factory tracker issues
• DRU-392 — docs: local issues tracker
• DRU-393 — appliance /mcp in issues builds
• DRU-485 — board cards open the ticket
• DRU-486 — inline ticket detail
• DRU-487 — tickets select a repo (drops IssuesProject)
• DRU-488 — markdown editor
• DRU-489 — fetch the Druks ticket, not a GitHub issue
• DRU-490 — Ready for Agent on a live build
• DRU-491 — align issue list cells on one baseline
• DRU-492 — Created by on the ticket sidebar
• DRU-493 — drag board cards between statuses

Risk

Alembic revisions for issues_* tables, then projects.prefix / ticket_seq and issues_tickets.repo_id. Unreleased stack: existing local tickets were not migrated; they are dropped rather than mapped.

Replay: Ready for Agent on a live run does not start a second workflow. Merge is still an external GitHub fact, not inferred from run lifecycle.

Verification

• uv run ruff check backend
• uv run ruff format --check backend
• uv pip install -e backend/tests/druks-field_notes
• uv run pytest backend/
• npm --prefix frontend run lint
• npm --prefix frontend test
• npm --prefix frontend run build
• Settings tracker issues labeled druks; no Services paste. Doctor is ok.
• Create a project with a prefix, add a repo, create a ticket against that repo. Identifier is {prefix}-1.
• Board and list show the ticket. The card opens detail. Description edits as markdown; the API still returns markdown.
• Ticket sidebar shows Created by, Created, and Updated.
• Drag a board card onto another status. The placeholder follows the pointer; drop commits that column. Same-column drop does nothing.
• Ready for Agent opens a build on the selected repo. In Progress / In Review write back. A second Ready for Agent on a parked review build does not start another run.
• With tracker issues, the sandbox can software_factory_get_ticket for BOX-3 and does not treat it as GitHub issue Subject keying rides DBOS workflow attributes; durable_runs shrinks #3.

Made with Cursor

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
druks	🟢 Ready	View Preview	Sep 10, 2026, 8:05 PM

💡 Tip: Enable Automations to automatically generate PRs for you.