Current documentation published at [1] has "Using the Mail Merge Wizard to create a form letter" section, that still mentions 8 steps (after the first screenshot with 5 steps, all other pages show 8), when that was changed in LibreOffice version 5.2. Our help [2] was updated for that. [1] https://documentation.libreoffice.org/en/english-documentation/writer/ [2] https://help.libreoffice.org/latest/en-US/text/swriter/01/mailmerge00.html See https://ask.libreoffice.org/en/question/218946
confirm
This has been updated in Getting Started Guide 6.4 and it has been updated in Writer Guide 6.4 which is due to be published.
I don't know why this was closed,help via F1 is still not correct. Help for Wizard needs an update so that's clear that Save, Print, Send are not a part of Mail Merge Wizard anymore, nor we have Create any longer. That remained from when Wizard had 8 steps. Note: Another improvement is to explain possible ways of using mail meege. Can be Wizard, but also simple adding of field in document using Data sources toolbar. So in Wizard help it should be clear when and why Wizard is useful.
*** Bug 141487 has been marked as a duplicate of this bug. ***
MailMerge in Writer DOES NOT generate mail-merged documents and does not produce an error message, just does nothing when hitting the "Finish" button, although all fields are in place; the same document and fields database produces multiple "substituted" documents with Writer version 5
> What Removed Added > Version 5.2 all versions 6.1.0.3 release > Component Documentation Writer Please describe why have you changed those fields for this bug, that is definitely about documentation, and is definitely since 5.2?
My complaint was NOT about documentation, it was about FUNCTIONALITY, a Bugzilla manager joined it with a former issue about documentation!
(In reply to Marc Nyssen from comment #7) "It was working some way in version X, and then it changed to work a different way in version X+1" is not a bug, as you were informed in your tdf#141487. Possibly your complaint was related to the fact that *documentation* was unclear about the intended operation since 5.2, which is why your bug was marked as a duplicate of this one. Yet, if you have some scenario that does not work anymore in newer versions, even if you use the new *intended* workflow, then your bug is different from this one (and you must make sure that you describe the problem in your bug in such a way that the bug is clear). Than that one is not a duplicate of this, but this still is a documentation bug. And it's still unclear why have you decided to change the version.