GitHub for Atlassian: Reverted Deployment to Production Not Reflected Releases in Development Panel

Question

Not sure if this expected behavior or not (I'm not used to this functionality!)

A Jira completed story was deployed within GitHub to Production, and this was correctly displayed in Jira as Released to Production. I can see all the correct Branches, Commits, etc., so the Webhooks, naming conventions, data are all working fine.

We then reverted this deployment via GitHub. However, this is not reflected in Jira, where it is telling me that it is still on Production.

What can be done so that I can mark this as not deployed to Production (or any other environment)?

Thanks

Saad Lagzouli · Answer

Adding to Arek's answer: GitHub has no "rolled back" deployment status, so the app never sends one, but you can send it to Jira yourself.

* In Jira, Settings > Apps > OAuth credentials: create a credential with deployment access.
* In the workflow that performs the revert, add a step that calls Jira's Deployments API (/rest/deployments/0.1/bulk) with state "rolled_back", environment type "production" and an association {"associationType": "issueIdOrKeys", "values": ["ABC-123"]} for the reverted issues.
* Jira groups deployments by pipeline and environment, so reuse the pipeline and environment the GitHub app already shows on the issue, with a higher sequence number. Try it on one issue first.

Redeploying the previous commit usually won't change the issue: the app links the commits that are new since the last deployment, and going backwards adds none.

Saad Lagzouli · Answer

Arkadiusz Wroblewski · Answer

Hello @Donald Nova

Problem laying on Github side. Jira does support a rolled_back deployment state, but GitHub doesn't provide a corresponding native rollback status. There is also an open request for this in the GitHub for Jira integration:

Is rolled_back status supported? · Issue #1793 · atlassian/github-for-jira

Best,

Arek🤠🧙‍♂️