nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

PR Created Trigger is not working

Kushagra Gupta_mhp1a5

I am trying to use PR Created Trigger under Dev Ops Rule. But it's not getting triggered.

Though all gitHub data(commit , PR , branches ) is shown correctly in development section of the issue.

Please help.

Accepted answers

All comments

Stefan Salzl

Hi @Kushagra Gupta and welcome to the community,

sad to hear that there are some problems. Keen to support you wherever I can.

Could you please add screenshots of your automation rule, an audit log and the issue where git-entities are connected and should trigger the rule?

Best
Stefan

Kushagra Gupta_mhp1a5

Hello @Stefan Salzl , Thanks for welcoming me to the community.

Below is the screenshot of the rule.

Screenshot 2022-03-16 at 4.26.48 PM.png

Below is the screenshot that GitHub is connected to Jira and we can see development info.

Screenshot 2022-03-16 at 4.28.19 PM.png

Below is the screenshot of the audit log. This rule is not getting triggered.

Screenshot 2022-03-16 at 4.32.16 PM.png

Hope it helps.

Stefan Salzl

hm.....that seems pretty weird as everything seems be set up fine 🙄

Regarding of the design of your rule I assume you are running on cloud right?
where and how is the PR created? (manually in GitHub? any automation/webhook?)

Best
Stefan

Kushagra Gupta_mhp1a5

Regarding of the design of your rule I assume you are running on cloud right? - YES
where and how is the PR created? (manually in GitHub? any automation/webhook?) - Manually , By developers.

Stefan Salzl

That‘s really weird. Can‘t reproduce this?

Did you try creating new branches and PRs for test?

Ome other thing (even if it sounds like common answer) would be to try to recreate the rule.

Otherwise I can‘t detect anything that would cause the problem. If it still ovcurs I would suggest to reach out to atlassian support. They are able too look deeper into the system and maybe detect any cause.

Best
Stefan

Kushagra Gupta_mhp1a5

I even tried creating another rule , adding a comment once branch is created.

That's also not working.

Screenshot 2022-03-21 at 11.25.32 AM.png

Amy McCann_oz7tuv

@Kushagra Gupta - Was this ever resolved? The same things is happening for us now. To troubleshoot, I created a very simple automation (just email fired when PR is created) and it's not firing. It's like Jira is not even recognizing that trigger anymore.

This has been working for our company FOR YEARS and just stopped firing 2 days ago. I have a ticket in and am working with Atlassian, but I am getting anxious, as it's ruining our workflow and we are on a very tight schedule.

Any tips you have would be appreciated!

Kushagra Gupta_mhp1a5

No , it was not resolved. We are using GitHub Enterprise edition and this functionality is NOT supported in JIRA with this edition of GitHub

Travis Hill_ovw34r

We are also seeing this as of two days ago. We're using Bitbucket, so I don't think it has anything to do with Github

Amy McCann_oz7tuv

@Travis Hill - We are using Bitbucket too!!! Last automation that fired was at 7:19 pm est on 3/20

This really does make me think that something is going on with on the Atlassian side!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

automation

pull-request