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
Bitbucket Server version 7.1.1.
The issue manifests on the Overview tab of a PR. A comment made on a certain line is displayed on the incorrect line on the Overview tab. On the Diff view, the comment is on the correct line.
I think this is happening when a comment is made on a custom diff (e.g. "changes since you last reviewed") and the comment is on a line that was not changed in that specific set of commits.
The overview tab recognizes that the comment was made on a specific commit, but it displays the comment on some seemingly random line.
Here is a specific example I ran into:
I add a comment on line 441 on the latest commit of the PR. There is a change on line 442, but line 441 has not been changed in this commit. The Diff view shows the commit correctly on line 441.
The Overview view shows the comment in the right commit, but it is located at line 461 of the file.
Anyone else running into this issue? If so, are there any workarounds (instead of manually adding the line number in the erroneous comment)?
(I know I am a few versions behind, but my brief look through the release notes didn't reveal anything like this bug. That doesn't mean it isn't fixed in the latest release, though.)
For future reference / whoever is reading this: open issue for this is https://jira.atlassian.com/browse/BSERV-12652 and seems to be Windows-specific (along with a bunch of other issues, such as https://confluence.atlassian.com/bitbucketserverkb/intermittently-pull-request-merges-fail-to-delete-branch-with-error-replacing-packed-refs-permission-denied-1050543943.html). Atlassian has no work around for these problems...