I want to automatically transition issues to "Awaiting Release" status, once the pull request is approved. This tells me that it will be merged soon and no one needs to do more work on it. For now, I need the reviewer to manually move it to that status.
@Muhammad Ramzan_Atlassian Certified Master_ Can we auto approve all commits automatically when workflow transition change? For example transition changed from In Review to Ready For QA then I have to approve all commits automatically on my repo in bitbucket.
Appreciate your help, Thanks in advance !!!
Create trigger on your jira workflow and then select the bibucket option , once pull request is approved this trigger will be triggered and transition will be changed.
https://confluence.atlassian.com/adminjiracloud/configuring-workflow-triggers-776636696.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply.
Pull request Approved is not on the list of available triggers for workflow transitions.
In addition, I want to be able to do this from the new automation rules.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My mistake i did not read about the pull request trigger.
If you have automation for jira then you can achieve this as follow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you using jira cloud by default you will have automation for jira plugin if you using server then its separate plugin provided by jira
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not really familiar with webhooks, so bear with me.... Here's my goal:
Q1: What option do you select for the webhook?
Q2: How does Jira find the associated ticket for any given pull request from the repo? Would I add a step to look up a ticket somehow or does it connect automatically?
Q3: Do I need a JQL Condition in place with a query like this?
assignee WAS in (557058:7f4cc0f9-6748-4551-8f01-ebf780d212e7) AND assignee in (557058:b05d092f-0845-429d-b6e3-80f1442ae8b1) AND project = FSS AND status = "CODE REVIEW"
I assume that it would be best to filter the tickets so that the correct developer was assigned, but with multiple developers on this project I wonder if there is an easier way to do this all together.
In other words: How would you configure this automation rule, exactly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use built in triggers by jira automation , here are the guidelines
https://www.atlassian.com/nl/software/jira/automation-template-library/bitbucket-github-gitlab
https://support.atlassian.com/jira-software-cloud/docs/smart-values-development/
In your commit message, jira issue key must exist then automation will know for which issue this rule will be executed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, but pull request approvals don't exist in the built in triggers in Jira Automation, so I'm not sure what I'm looking for in the documentation. How did you configure the webhook to pull in the title/issue ID and user ID from the pull request POST body?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Lissa Meade , Pull request approval trigger does not exist. To achieve this , please follow the steps as below.
You need to perform some steps on Jira & Bitbucket side.
Below is the link for your guide, its not same as you trying to achieve but it will give you the flexibility to implement your automation rule.
https://blog.codebarrel.io/how-to-integrate-jira-and-github-using-automation-part-2-5eb816f2b947
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Muhammad,
Is there any movement on this issue? We would like to be able to implement more formal rules based on bitbucket pr approvals. If not, can you rehost the information that was on codebarrel? The link seems to have expired. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.