Menu

Stop Manually Updating Jira After Every PR Merge
πŸ–ΌοΈ

Stop Manually Updating Jira After Every PR Merge

DEV CommunityΒ·Glenn GrayΒ·6 months ago
#9bYkNGif
#githubactions#jira#cicd#ticket#github
Reading 0:00
15s threshold

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.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.