DRU-391 - Treat the local issue board as a Software Factory tracker - #419
Open
chaosk wants to merge 1 commit into
Open
DRU-391 - Treat the local issue board as a Software Factory tracker#419chaosk wants to merge 1 commit into
chaosk wants to merge 1 commit into
Conversation
chaosk
force-pushed
the
agent/DRU-390-2
branch
from
September 7, 2026 21:43
a8d8003 to
996ee13
Compare
chaosk
force-pushed
the
agent/DRU-391
branch
from
September 7, 2026 21:43
9e42751 to
7ae66b4
Compare
8 tasks
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>
chaosk
force-pushed
the
agent/DRU-390-2
branch
from
September 7, 2026 22:01
996ee13 to
ffa689d
Compare
chaosk
force-pushed
the
agent/DRU-391
branch
from
September 7, 2026 22:01
7ae66b4 to
c99459c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linear ticket: DRU-391
Stacked on DRU-390.
Summary
SoftwareFactory.Settings.trackergains"issues". The select shows druks via existingchoice_details; the stored value staysissues.IssuesTrackerwrites status throughTicket.transition. No Service identity, no webhook.local issues boardas ok. Trackerless (none) is unchanged.Test plan
uv run ruff check backenduv run ruff format --check backenduv pip install -e backend/tests/druks-field_notesuv run pytest backend/issues, labeleddruks; Linear/Jira status-name fields hide.druks doctorreports the issues tracker as ok without any Services paste.IssuesProject.namematching a registered repo's bare name, opens a Build withWorkItem.source == "issues".