We already have Jira integrated with github, so any mention of Jira ticket in commits links them together. Now we would like to change the mergeability of a PR based on the status of its associated ticket.
I did check out a similar question: https://community.atlassian.com/t5/Bitbucket-questions/Prevent-merge-based-on-JIRA-status/qaq-p/1169454,
but this was about BitBucket.
Is there any "Atlassian" way currently? If not, what are the ways to manually enforce this? Github actions? Webhooks? Please help.
Thanks.
Any resolution on this? Would love to know if you were able to solve this and how.
No @Eugene Lorman I didn't do anything about it. If you find any plugin for it, let me know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We ended up creating a custom github action (3 of them) to help pull in jira labels and treat them as check for a PR. Can probably DM if someone else needs this and is maybe interested in packaging as a single action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Eugene Lorman would love to see what you created. Not sure if/how you can DM here, but a reply here might benefit others anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with @James Sheridan . @Eugene Lorman , would love to see what you did as we are running into the same issue where this could be the solve for us. Any way you could share?
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.
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.
There is not but what use case do you have where a dev needs to check jira before merging a PR?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Say the PR branch is deployed to staging and QA does testing on it. We want to ensure that the PR gets merged to master only when the QA marks the ticket as resolved.
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.