You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
When reviewing Pull Requests (PR) on Github, the common options are to (1) comment (either in-line or top level comments), (2) approve, and (3) request changes. The triggers offered by Jira to automate actions based off of PRs are the following:
PR Created
PR Declined
PR Merged
I haven't yet looked into whether finishing a PR review with Comment or Request changes will trigger the PR Declined hook, but I believe it may be best for those to be separate, as Github has them separate.
Checked this functionality just now. Sorry for double post.
Requesting changes does not trigger the automation. But Closing the PR does.
I would suggest to create individual triggers for finishing a PR with "Comment", and "Request Changes". And I would also rename the "Declined" PR trigger to "Closed", since that is what Github calls it.
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...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.