Skip to content

Set Priority = P1 and Status = Backlog on auto-created PR tracking issues - #1297

Merged
hilram7 merged 1 commit into
devfrom
hilram7/kb-ops-priority-p1-backlog
Jul 31, 2026
Merged

Set Priority = P1 and Status = Backlog on auto-created PR tracking issues#1297
hilram7 merged 1 commit into
devfrom
hilram7/kb-ops-priority-p1-backlog

Conversation

@hilram7

@hilram7 hilram7 commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Tracking issues created by auto-create-pr-tracking-issues.yml (both the Admin Support and Publishing Pipeline jobs) now get Priority = P1 instead of P2.
  • Both jobs now also set Status = Backlog on creation, so tracking issues never land on the project board without a status.

Changes

  • .github/workflows/auto-create-pr-tracking-issues.yml: replaced the Priority = P2 (5280356b) field mutation with Priority = P1 (c2ae6a84) in both jobs; added a Status = Backlog (f75ad846) field mutation in both jobs.

Testing

  • No local execution (workflow only runs on pull_request: review_requested events) — verified field/option IDs against the live project schema via gh api graphql against netwrix/projects/2 before editing.
  • actionlint not run in this environment; no syntax changes beyond two setField call edits, following the existing setField helper pattern already used elsewhere in the file.

…sues

Ensures new tracking issues surface at the correct priority and never land on the board without a status.
@github-actions

Copy link
Copy Markdown
Contributor

Code Review

No correctness, security, or workflow issues found.

The change is limited to the setField calls in both jobs of auto-create-pr-tracking-issues.yml:

  • Priority option changed from P2 (5280356b) to P1 (c2ae6a84).
  • A new Status = Backlog field (PVTSSF_lADOB435Ds4A7py9zgv4xF8 / f75ad846) is set in both jobs.

Both new/changed calls reuse the existing setField helper with the same signature and error handling as the surrounding, already-working calls, so the control flow, permissions (GITHUB_TOKEN locked to none, all calls via KB_OPS_PAT), triggers, and idempotency logic are unaffected.

One thing I could not verify from the diff: the field ID PVTSSF_lADOB435Ds4A7py9zgv4xF8 and option ID f75ad846 for the new Status field, and the new P1 option ID c2ae6a84, are opaque project-board identifiers. If any is wrong, setField will log a ✗ Failed to set ... error but will not fail the job (errors are caught), so a bad ID would silently no-op rather than break the build. Worth a quick confirmation against the project board that these IDs are correct.

@hilram7
hilram7 merged commit de5f05b into dev Jul 31, 2026
8 checks passed
@hilram7
hilram7 deleted the hilram7/kb-ops-priority-p1-backlog branch July 31, 2026 04:34
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