Bug 123082 - FILESAVE RTF Copied mail merge field loses its link type when saved in LO
Summary: FILESAVE RTF Copied mail merge field loses its link type when saved in LO
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:rtf
Depends on:
Blocks: Fields RTF-Fields
  Show dependency treegraph
 
Reported: 2019-01-31 09:06 UTC by NISZ LibreOffice Team
Modified: 2022-08-09 22:19 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
The original document. (15.39 KB, application/rtf)
2019-01-31 09:07 UTC, NISZ LibreOffice Team
Details
The saved file. (15.82 KB, application/rtf)
2019-01-31 09:07 UTC, NISZ LibreOffice Team
Details
Screenshot of the original and exported document side by side in Writer. (267.56 KB, image/png)
2019-01-31 09:08 UTC, NISZ LibreOffice Team
Details
he database for the mail merge field. (27 bytes, text/plain)
2019-01-31 09:08 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2019-01-31 09:06:28 UTC
Description:
When the UGYFEL field, inserted with Word gets copied and pasted in the attached file and reloaded the copy loses its field type. The original field retains its field formatting. The problem also happens when a new mail merge field is inserted via the Fields dialog and saved as RTF.

Steps to Reproduce:
    1. Open the attached document.
    2. Copy and paste the UGYFEL field.
    3. Save and reload.

Actual Results:
The copy is no longer a field. The original still is.

Expected Results:
The copy should still be a field even after saving.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 NISZ LibreOffice Team 2019-01-31 09:07:11 UTC
Created attachment 148792 [details]
The original document.
Comment 2 NISZ LibreOffice Team 2019-01-31 09:07:29 UTC
Created attachment 148793 [details]
The saved file.
Comment 3 NISZ LibreOffice Team 2019-01-31 09:08:04 UTC
Created attachment 148794 [details]
Screenshot of the original and exported document side by side in Writer.
Comment 4 NISZ LibreOffice Team 2019-01-31 09:08:19 UTC
Created attachment 148795 [details]
he database for the mail merge field.
Comment 5 Durgapriyanka 2019-01-31 18:04:30 UTC
Thank you for reporting the bug. I can confirm the bug in

Version: 6.3.0.0.alpha0+
Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Comment 6 Buovjaga 2019-02-10 16:50:04 UTC
Same result in 5.3.0, 4.3.0, 3.3.0 (Win 10).
Comment 7 QA Administrators 2022-01-19 03:34:23 UTC
Dear NISZ LibreOffice Team,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug