---
title: "Discussion on \"Stop Manually Updating Jira After Every PR Merge\" | Hashnode"
description: "Discussion on \"Stop Manually Updating Jira After Every PR Merge\". Originally published on graycloudarch.com.\n\nYou 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 minute..."
url: "https://hashnode.com/posts/stop-manually-updating-jira-after-every-pr-merge-1/69f9e336a54cd251b367e150"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Stop Manually Updating Jira After Every PR Merge](https://tallgray.hashnode.dev/stop-manually-updating-jira-after-every-pr-merge-1?utm_source=hashnode&utm_medium=feed)

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

May 5 · 6 min read · tallgray.hashnode.dev  
Read the article

-   [#github-actions](https://hashnode.com/tag/github-actions)
-   [#jira](https://hashnode.com/tag/jira)
-   [#cicd](https://hashnode.com/tag/cicd)
-   [#automation](https://hashnode.com/tag/automation)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Glenn Gray](https://hashnode.com/@tallgray)

@tallgray · Denver, CO

  
[View profile](https://hashnode.com/@tallgray)

Infrastructure Architect · AWS · Kubernetes · Terraform

I design multi-account AWS platforms, EKS/ECS clusters, and Terraform IaC that production teams can own and maintain. Writing about what I learn from real-world infrastructure work.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
