You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
@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!
Any guess on how long it will take to resolve? This is my first real bug with Atlassian, and I am a bit worried that we are going to go into a black hole, lol.
@Amy McCann I haven't gotten any update since the initial response:
Marcelo Beloni commented:
I hope you are doing well!
Thanks for contacting Atlassian Support. My name is Marcelo, and I will be assisting you with this ticket.
We're currently investigating an incident where the pull request triggers are not being fired on Automation. Our dev team is already working to fix it.
We will provide more information as we work to identify the root cause.
We apologize for the inconvenience.
For us, it started stopping again today. We created a second rule that triggers upon PR creation and since then none of the rules get triggered anymore.
Any idea why this could happen again?
The ticket which got resolved seemed to have only resolved issues when a PR got merged
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.
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?
Hello @Stefan Salzl , Thanks for welcoming me to the community.
Below is the screenshot of the rule.
Below is the screenshot that GitHub is connected to Jira and we can see development info.
Below is the screenshot of the audit log. This rule is not getting triggered.
Hope it helps.
hm.....that seems pretty weird as everything seems be set up fine 🙄