Auto-add new issues to the Stacklok Engineering board to reduce untracked/unlinked work #11

User story

As an engineering manager, I want every new issue to be automatically added to the Stacklok Engineering board, so that issues don't go untracked and PRs that reference them aren't flagged as unlinked to a tracked item.

Problem

Issues opened in a repo don't automatically land on project 73 (Stacklok Engineering). When an issue is never added to the board, it's effectively untracked — and PRs that link to it still count as "linked to an issue" per check-pr-issue-link.yml, but the underlying work has no visibility on the board. This contributes to a gap between "PR has a linked issue" and "the linked issue is actually tracked," undermining flow-metrics and planning visibility.

GitHub's built-in Projects "Auto-add to project" automation only supports one rule per repo, with no way to add a second repo or a second parallel rule — so it can't be centrally configured to cover every repo in the org from the project side.

Solution

A reusable workflow_call workflow, add-issues-to-project.yml, that any repo can call on issues: opened to add the new issue to a specified Projects v2 board and set an initial Status — without relying on the built-in per-repo automation.

Acceptance criteria

• stacklok/.github exposes a reusable workflow at .github/workflows/add-issues-to-project.yml that accepts a target project/status configuration and adds the triggering issue to that board.
• stacklok/claude-plugins (the original source of this logic) calls the reusable workflow instead of maintaining its own copy.
• Newly opened issues in repos that adopt the workflow appear on project 73 with an initial Status set, without manual intervention.

Related

• Reusable workflow implementation: feat: add add-issues-to-project reusable workflow #10