This week we've had multiple occasions when a PR was merged but it then updated several unrelated tickets. We haven't changed anything in our Jira configuration for this, and in both cases I can't see any reason why the PR could be linked to the tickets it updated. Has something changed it bitbucket that could affect this?
I have the same problem.
A PR was created in BitBucket. This PR is now attached to multiple unrelated JIRA tickets. There is no mention of the unrelated tickets in any of the commits pertaining to the PR.
Could do with solving this quite urgently as it's causing a massive headache working out which tickets have actually been merged and which are still under review.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot