Triggering Automation to Transition Tickets Once Server is Built

[Kaladin Stormblessed]

hello all, the last 2 statuses of our workflow are "QA Approved" and "Released". A ticket is marked as released when the QA approved tickets are pushed to the server, when its updated every few days. At times, the QA approved ticket numbers can be quite large. Is there any way I can create an automation that gets triggered every time I push QA approved changes to the server, such that it transitions the issues to "Released" from "QA Approved"?

[Mark Rekveld - Marvelution · Accepted solution]

Taking a look at the marketplace there are loads of apps available in the CI/CD and automation space. Mine for instance Jenkins for Jira is specific for Jenkins, but there are other options as well.

But as Vishal expressed already, what is your CI/CD tool of choice?

[Kaladin Stormblessed]

We use github actions at the moment. 

[Vishal Biyani · Accepted solution]

@Kaladin Stormblessed 

What is your build system?

How does it notify back to JIRA that build is complete?

[Kaladin Stormblessed]

At the moment, we have no notification when the build is complete. We manually update it. That's why I am asking if there's a quicker way to do this. 

[Vishal Biyani]

What is your build system? Is it Jenkins or something else?

[Kaladin Stormblessed]

We use GitHub actions at the moment. 

[Vishal Biyani]

@Kaladin Stormblessed 

Go through this article that talks about integrating git hub with JIRA. See if this helps.

https://support.atlassian.com/jira-cloud-administration/docs/link-github-workflows-and-deployments-to-jira-issues/

[Kaladin Stormblessed]

Thank you so much!