Sometimes octave transposing causes chord offset

(Using MuseScore 3.0.5)

I regret having to report something that cannot be easily reproduced since it seems to happen randomly.

It happened several times that after an octave shift of a selection using Ctrl-Down or Ctrl-Up one or more notes don't end at the expected position, though they sound at the right pitch. Looking at the properties in the Inspector, I find that they have a chord offset, for instance, by 2 spaces. May be somebody that has experienced the same issue is able to specify better the conditions under which this occurs.