URGENT: Jira + Github with "automerge-action"

Question

Hello community,

I need help with Jira + Github integration (automerge-action).

We use the Jira Cloud integrated with Github. We have an integration responsible for moving a card in our workflow to the Delivered status whenever a Pull Request Merged occurs.

This Pull Request Merged can occur in two ways:

1 - Manually through Github's "Merge pull request button": https://github-images.s3.amazonaws.com/enterprise/2.20/assets/images/help/pull_requests/pullrequest-mergebutton.png

2 - Through an action (automerge-action): https://github.com/pascalgn/automerge-action.

Our problem:

- When we do it by option 1, our Jira automation captures the request and the card movement occurs normally.

- When we do option 2, our automation does not capture the request and the card movement does not happen, and also, we have no error log in the Jira automation to detect the problem.

Notes:

- On Github the Pull Request Merge operation is completed in both cases.

- In Jira, (when executed by the automerge-action option) the issue remains with the Pull Request status OPEN, it's as if Pull Request Merged hadn't happened on Github

Attached are two files.

The first one to show that in Jira the issue remains in status IN PROGRESS and with the Development status OPEN, even after the Pull Request Merged is completed on Github.

The second image to show the automation responsible for moving the issue in Jira.

Dionei Piazza · Answer

Hello @Yvan Martin

Thanks for your help! We just created an issue for the person responsible for this GitHub third-party project. 👍

Yvan Martin_qxvthw · Answer

Hi Dionei,

Looking at the library you mentions it does note the following limitation:

* When a pull request is merged by this action, the merge will not trigger other GitHub workflows. Similarly, when another GitHub workflow creates a pull request, this action will not be triggered. This is because an action in a workflow run can't trigger a new workflow run. However, the workflow_run event is triggered as expected.

My understanding is GitHub internally uses workflows to notify third parties like Jira DevOps events, so that would explain why regular merge events are coming through but not ones generated by that plugin. This sounds like it might be something to check with GitHub or that library provider on ways around getting other GitHub workflows events to trigger as normal.

Cheers.