Handle GitHub issues transferred between repositories (RDT-1268) (SRV-176)

[Copilot]

When a GitHub issue is transferred between repos, both the source and destination sync actions run independently—resulting in two Jira issues for the same GitHub issue, with both keys appended to the title (e.g., Title (IEP-123) (IDFGH-456)).

Changes

sync_issue.py — new handle_issue_transferred()

Handles the issues:transferred webhook event fired in the source repo:

• Finds the existing Jira issue via the old GitHub URL's remote link
• Updates the remote link globalId to the new GitHub URL so the destination repo's sync action can find it by URL lookup (preventing duplicate creation in the happy path)
• Updates the Jira issue summary and description to reflect the new issue number/URL
• Leaves a Jira comment documenting source → destination transfer

sync_issue.py — modified _find_jira_issue()

Adds a transfer detection fallback for the destination repo to handle the race condition where opened fires before the source repo's transferred handler has run:

When no Jira issue is found by URL, and the GitHub title contains a Jira key (e.g., (IEP-123)), the existing manual-sync logic already checks if IEP-123 exists. This now also checks if that issue has a synced from remote link starting with https://github.com/—indicating a previously synced issue from another repo. If detected, the remote link is updated to the new URL and the existing issue is returned, skipping creation.

sync_to_jira.py

Registers handle_issue_transferred under the issues:transferred action in the dispatch table.

Tests

Six new tests covering: remote link update, graceful no-ops for missing Jira issue or missing new_issue payload, transfer detection in _find_jira_issue, duplicate prevention in handle_issue_opened, and routing of the transferred event.

---

⌨️ Start Copilot coding agent tasks without leaving your editor — available in VS Code, Visual Studio, JetBrains IDEs and Eclipse.