New automation triggers across Jira Cloud, Bitbucket, GitLab & Github!

[Dean Comiskey]

Thanks @Braden for the quick reply. I contacted support but I think you have the answer above. Server is the forgotten child :(

[Braden]

@Dean Comiskey Yea man...exactly.  Its a bummer.  You guys considering migrating?  I still wanna see what @John McKiernan knows about possible Data Center support for this feature.

[Dean Comiskey]

@Braden Yes we are exploring both DC and Cloud atm. Would also be interested in @John McKiernan response regarding this functionality in DC.

[John McKiernan]

Hey @Dean Comiskey @Braden 

Thanks for the messages. Braden is correct here. These newest triggers are only available in Jira Cloud and not Jira Server or Data Centre. To be transparent, to my knowledge they won't be built out for Server/DC in the future as the automation team are Cloud-focused. I know it's frustrating but Atlassian have tried to be as open as possible about being Cloud-first. 

Sorry it's not the answer you are looking for but let me know if you have any other questions.

John 

[Olga Buslovich]

@John McKiernan HI!!

I'm really excited about the DevOps and Webhook additions to the automation rules for JIRA cloud. Our teams at Fyusion are using them a lot and very happy about the provided solutions  - THANK YOU!!

I'm writing to ask for you advise with one of the rule that I've been asked to create for the Dev team. The use cases are as follows: 

UC#1

There is an opened Pull Request in the Github that got set to "review_requested" . The ask here is to create an automation rule that would move the associated JIRA to the status "Code Review" and send an email to the dev team that there is PR pending review.

Here is the Automation Rule that I came up with:

The rule gets triggered by the Github webhook that has "Pull Request" and "Pull Request Reviews" options selected.

There are two conditions that search the  webhook payload sent from Github and if they met then the status of associated JIRA ticket gets set to "Code Review" in JIRA and the email sent to the dev team.

The following JQL narrows down the search to the JIRA key that is a part of the PR title in Github:  key= "{{webhookData.pull_request.title.substringBetween("[", "]")}}"

The problem i'm facing seems related to the following events missing from the payload JSON in JIRA. I do see all of them being included in the payload that sent from Github but none of these are shown in the Audit Log in JIRA (i.e. there is no response data for "action"or "review").  The payload Github is sending has everything but for the same payload, JIRA only picks up the things for the key "pull_request" and ignores everything else.

{{pull_request_review.action}} = submitted

{{webhookData.pull_request.action}} = review_requested

pull_request_review.review["state"] = approved

 I did open a support ticket w/ JIRA and they have suggested that " that these operations are related to one of the operations supported natively by A4J".

So my question for you is there a way to fix that automation rule using webhook or maybe there is better solution here? Please advise!

Thanks in advance,

Olga

[John McKiernan]

Hey @Olga Buslovich ,

Delighted you are getting good use out of these triggers! That's the goal :)

To be honest, I am not sure of the answer to your question here. It goes beyond my non-dev marketing brain! 

I know you have already raised a ticket with Jira support. I want to make sure you aren't running around in circles trying to get an answer. 

"These operations are related to one of the operations supported natively by A4J". This is correct but the support engineers should hopefully be able to either solve it or escalate it to one of the team trained in automation who can dig into it. 

Sorry I can't help directly but hopefully this helps!

John 

[Olga Buslovich]

Thanks for your feedback,  @John McKiernan !!

I'll follow up with the JIRA support and share the solution (if there is one!) or the workaround once it gets addressed.

Best,

Olga

[Eli Lansey]

How does this work with corporate hosted Jira and Bitbucket instance (rather than "cloud")?

[Dave Liao]

@Eli Lansey - these triggers aren't available with on-prem Jira (Server, Data Center).

Looks like someone made a ticket requesting this, you can vote it up! (I have!) https://jira.atlassian.com/browse/JIRAAUTOSERVER-20