Code suggestions were introduced in Bitbucket 6.6.0:
User opened a github issue:
This bug report came in through github, we should push out another free release fixing this before the first paid release, because it led to the user in question downgrading. Can one of you take a look?
I will do.
when you start working on this, can you fork off of tag 1.2.5? It will be easier to do that then fork off of master and then have to cherry pick the commit.
Investigated issue, reproduced with version 1.25. The cause is which enables checking changes made from Bitbucket UI, including Apply suggestions feature, which doesn’t display the reasons of reject and don’t allow to edit suggestion after it’s rejected once. I have left a feedback to Atlassian on this topic.
99% that commits initiated with Apply suggestion feature mentioned by customer are correctly rejected, but there’s no way for him to understand why. I have answered to customer how to get reject reason from Bitbucket logs.
I have created for adding new options since it is not a bug actually. I can deal with it in short.
Further suggested steps:
implement based on latest released 1.25
release it separately as free 1.26 version
close this issue
Will be addressed in scope of YACC-267.