Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

URGENT: Jira + Github with "automerge-action"

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.

MergedOnGitOpenInJira.PNG

 

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

AutomationMoveToDelivered.PNG

1 answer

0 votes
Yvan Martin Atlassian Team Dec 17, 2020

Hi Dionei,

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

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.

Hello @Yvan Martin

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

750 views 12 19
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you