Broken Jira callers remain after reusable workflows were removed

[ryanduguid]

Summary

Commit 7688d3a removed Jira issue management from this repository on 18 May 2026, including these reusable workflows:

• .github/workflows/jira_create_issue.yml
• .github/workflows/jira_update_issue_closed.yml
• .github/workflows/jira_update_issue_reopen.yml

GitHub code search currently finds 41 XeroAPI repositories still calling each deleted path at @master (123 caller references in total). Those issue-opened, issue-closed and issue-reopened workflows now resolve to missing reusable workflow files.

One concrete example is XeroAPI/xero-php-oauth2 at current master (e103bc4), where all three callers still target the deleted paths. This was found while preparing xero-php-oauth2 #433; that PR intentionally changes permissions only and does not make the separate behavioural decision to restore or retire Jira integration.

Current evidence

• Current Xero-OpenAPI master: 853dc01a99c179d21df3a0b4f870ed612aebf3e3
• All three former paths return HTTP 404 on current master
• Current workflow tree contains only api-diff.yml, create-github-release.yml, pr-linting.yml and pr-validation.yml
• The three former workflows have no compatible replacement path in this repository
• Exact organisation code-search counts on 14 August 2026: 41 create callers, 41 close callers and 41 reopen callers across 41 repositories

Suggested resolution

Please decide once at organisation level whether Jira issue automation remains supported:

1. If supported, restore compatible reusable workflows at the old paths or update all callers to a maintained repository and immutable ref.
2. If retired, remove the three dead caller workflows across the affected repositories.
3. In either case, avoid mutable @master references and review whether broad secrets: inherit is still required.

A coordinated fix will avoid dozens of repository-specific patches and preserve one source of truth for the intended Jira lifecycle.