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
Hi Luis, updates to a file in a pull request can cause comments to disappear. We attempt to put the comments back on the correct line however this is not always possible (for example when the line is removed from the file).
I don't know the particulars about your case, so I'm not able to tell whether or not your comment should have been removed or not.
The Bitbucket team wrote a detailed description about this behaviour at Building inline comments for pull request and commits (see the "High Plains Drifter" section). This might help you understand how this issue is approached.
Lastly, are you using Bitbucket Cloud or Server? For Server, we have a feature request at BSERV-7534 You can vote for it or add your comments.
Hope this helps!
Thanks for the response.
It's not the case. We are using at this moment Bitbucket Cloud for the first time and trying it.
In this particular case, we made a commit modifying a line with a comment and it disappear. This commit the only thing that does is renaming a variable in the line so it's very strange.
Yes we read the documentation about the "Hight Plains Drifter" and we thought the comment wasn't going to be removed.
Generally, if the line changes, it's in response to the comment(s), so the PR diff view hides comments that are possibly obsolete.
Look for a number next to the "Side-by-side diff" button on a file's header, like the 2 in this screenshot; if you click that, then you should be able to see the hidden comments on that file.
Ah ok. That's the normal behaviour, the comment disappearing after a change on the line.
We though is a little hard to review the changes after the comment is gone. We need to open the box with the number "2" (on your example) a view what comment were made and in what lines to make sure the changes are fixed. Maybe we are using it wrong.
@jredmond What about the case where a side-by-side diff is not allowed?
In this case, it seems that the comments are hidden as obsolete in the Unified View, but since the file is considered new, the side-by-side diff is not allowed.
Could you make a way to see pull request diff at the state when was made the comment?
Now pull request shows diff from latest code. In other words - diff from specific commit and code where we want to merge to.
Also the code where we want to merge to might change. So migth be not fully solvable. But still better.
And for that case maybe just add screenshots of the code and comments.
Hi, Atlassian Team!
When a file is renamed in the PR, the PR displays the contents of the file as all new even though nothing may have been changed at all in the file contents.
This creates a lot of problems for code review.
Do you consider this acceptable behavior? Are there any moves in this direction?