Stop Manually Updating Jira After Every PR Merge

This post was originally published on graycloudarch.com. You just merged a PR. Now you open Jira, find the ticket, paste the PR link in a comment, transition the status to Done, and update the deployed field. Five minutes. Twenty times a week. That's 1,700 minutes per year per engineer --- nearly 30 hours of pure mechanical overhead. And that's assuming you remember. On one team I worked with, we audited the last three months of merged PRs. Thirty percent of tickets had no update after merge. No comment, no transition, no link. The ticket just sat in In Dev until someone noticed during sprint review. The fix is two GitHub Actions workflows and a shared composite action. Here's exactly how to build it. The Architecture Two workflows, one shared extraction layer: Workflow 1: Fires on PR creation --- posts a Jira link comment to the PR so reviewers can navigate directly to the ticket. Workflow 2: Fires on PR merge to main --- posts a comment to the Jira ticket with the PR URL, commit SHA,