Description: While setting up a mailmerge at the step adress block the option 'supress line with just empty fields' has no impact, e.g. an empty line is visible in the adress block. Steps to Reproduce: 1.set up a mailmerge using the wizard from tools 2.at step adress block mark option 'supress....' 3.look at the adress block created on the document Actual Results: empty line in the adress block (CR) Expected Results: no empty line in the adress block where the field in the adress base is empty. (probably a CR should be supressed when option chosen). Reproducible: Always User Profile Reset: No Additional Info: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; Locale: en-US (en_US.UTF-8); Calc: group happens also with release 5.3 User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36
Not reproduced. I tested it by going to the mailmerge meta and hunting for some example data. I gave up quickly and picked attachment 127721 [details] which is just an ODS, created a new database using it as source. I added a column "empty" to the ODS without entering any data under it - I understand this is what you meant. I edited the address line block in the Mm wizard, removing any unneeded ones and matched the 3 fields randomly to title, first name, last name. I saved the merged document as one file and there was no empty paragraph in place of the "empty" db field. Please test with LibreOffice 5.4 and/or 6.0 pre-release. An easy way on Linux: http://libreoffice.soluzioniopen.com/ Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: 2d8f17565ebe867210f5769851d91b2e7b612a8f CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on January 27th 2018 Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180731
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180903