DRU-695 -- Start a tracker build under the person who moved the ticket - #805
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
czpython
force-pushed
the
codex/issue-790-tracker-actor
branch
from
October 3, 2026 16:28
baf3611 to
4dfc14e
Compare
czpython
changed the title
czpython
force-pushed
the
codex/issue-790-tracker-actor
branch
from
October 3, 2026 16:38
4dfc14e to
fa7ffab
Compare
This branch was successfully deployed
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
1 participant
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.
A Linear or Jira build now runs under the Druks account of the person who moved the ticket. If that person has no account, the build uses the assignee's account, and then the default account.
Linear names that person in the webhook's
actor. The Jira Automation body has no such field, so the operator's rule sends{{initiator.accountId}}in anx-jira-initiatorheader. Both arrive asactor_idin theticket.transitionedpayload, besideassignee_id. The board does not report who moved a ticket yet, so it sendsNoneand keeps building under the assignee.Fixes #790.