Skip to content

DRU-391 - Treat the local issue board as a Software Factory tracker - #419

Open
chaosk wants to merge 1 commit into
agent/DRU-390-2from
agent/DRU-391
Open

DRU-391 - Treat the local issue board as a Software Factory tracker#419
chaosk wants to merge 1 commit into
agent/DRU-390-2from
agent/DRU-391

Conversation

@chaosk

@chaosk chaosk commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

Linear ticket: DRU-391

Stacked on DRU-390.

Summary

  • SoftwareFactory.Settings.tracker gains "issues". The select shows druks via existing choice_details; the stored value stays issues.
  • IssuesTracker writes status through Ticket.transition. No Service identity, no webhook.
  • Doctor reports local issues board as ok. Trackerless (none) is unchanged.

Test plan

  • uv run ruff check backend
  • uv run ruff format --check backend
  • uv pip install -e backend/tests/druks-field_notes
  • uv run pytest backend/
  • Settings offers tracker issues, labeled druks; Linear/Jira status-name fields hide.
  • druks doctor reports the issues tracker as ok without any Services paste.
  • Ready for Agent, with IssuesProject.name matching a registered repo's bare name, opens a Build with WorkItem.source == "issues".
  • A Ready for Agent ticket whose project name matches no repo still skips.

@chaosk
chaosk requested a review from czpython as a code owner September 4, 2026 05:10
@chaosk chaosk changed the title Treat the local Issues board as a Software Factory tracker. DRU-391 - Treat the local issue board as a Software Factory tracker Sep 7, 2026
Selecting druks needs no Service identity: status writes go through Ticket.transition and the existing funnel opens the build.

Co-authored-by: Cursor <cursoragent@cursor.com>
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