Skip to content

DRU-392 - Docs: local issues tracker - #479

Open
chaosk wants to merge 1 commit into
integration/issuesfrom
agent/DRU-392
Open

DRU-392 - Docs: local issues tracker#479
chaosk wants to merge 1 commit into
integration/issuesfrom
agent/DRU-392

Conversation

@chaosk

@chaosk chaosk commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Rewrite the public guides so the local board matches integration/issues: Software Factory tracker druks (stored as issues), prefix on the GitHub project, tickets select a repo, Ready for Agent opens a build.
  • Full-local and quickstart no longer imply every tracker needs Settings → Services. Local-board builds use this appliance's /mcp (software_factory_get_ticket / software_factory_add_comment), not Linear MCP.
  • Author guide: the board is Software Factory policy, not a second app or a Service kind.

Test plan

  • Read Ticketing integrations against Software Factory → Settings with tracker druks.
  • Confirm full-local webhook caveat still lists GitHub/Linear/Jira paths and states the local board needs no tracker credentials.
  • Confirm writing-an-app does not introduce an Issues namespace.

Made with Cursor

…ior.

The tracker is druks on this appliance, not a separate Issues app, and
builds fetch the ticket from /mcp.

Co-authored-by: Cursor <cursoragent@cursor.com>
@chaosk
chaosk requested a review from czpython as a code owner September 8, 2026 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant