If I use the “Move / Rename” feature, the History of the page gets a new version.
The new version does not have my name, it has the name of the previous person that modified the page. I see this as a bug.
In the History, it appears as
edited by UnsuspectingRetiredPerson
on 11/09/2026 10:14:40
Change comment: Update document after refactoring.
On the page, it appears near the top as
Last modified by UnsuspectingRetiredPerson on 11/09/2026 10:14:40
If/When a new version is created, it should get the name of the person that triggers the change. Certainly not someone that was not present/active.
My preference is that there is no new version of the page when the page is simply moved, with no content change. But I’m no wiki/knowledge expert.
Do you also see this as a bug ? Should I report it through some other channel ?
so to give a bit of technical context: when the page move there’s some metadata that are changed, so you do need a new version to properly keep history of those changes. And the reason why we reuse the author of last version is to not break anything: for example, let’s assume your last author had some script right and inserted a script, and you don’t have script right: if you move the page and we use you as author, we’re breaking immediately the execution of the script in the page.
Now I agree that it might indeed be confusing in terms of UX to see people not supposed to be around anymore being author of new changes due to that. Would be interesting to have opinions from others on this.
Maybe there could be an author for the “content” (unchanged after the “Move”) and an author for the “metadata” (changed by the “Move”). Sounds like a can of worm.
Maybe there could be changes that must be reflected in the “Last modified by”, and changes that shouldn’t be reflected in the “Last modified by” (like moving the page). I guess some users would then complain about lack of transparency.
OK, maybe no clean/easy solution.
Enjoy the week-end.
Ahah so technically there is but I think we’re actually displaying the metadata author (might be wrong here)
Now we do have a concept of effective vs displayed author that we could use in that specific refactoring usecase and maybe that would make sense indeed.
That’s actually an interesting point, I don’t remember what separation we make between what’s indicated in “Last modified by” and what’s indicated in the history.