Bug 121470 - After pressing the "Reset Properties" button - when pressing the "OK" button the time on the "Created" field is being reset again (on Properties - General)
Summary: After pressing the "Reset Properties" button - when pressing the "OK" button ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: File-Properties
  Show dependency treegraph
 
Reported: 2018-11-16 19:19 UTC by Liad Skiva
Modified: 2023-10-04 19:32 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Liad Skiva 2018-11-16 19:19:40 UTC
Description:
After pressing the "Reset Properties" button, and the time in "Created" is reset, pressing the "OK" button resets the time again to the time when pressing the "OK" button.

Steps to Reproduce:
1. Go to File->Properties.
2. Press the "Reset Properties" button.
3. Wait a few seconds.
4. Press the "OK" button.
5. Go to File->Properties.

Actual Results:
When returning to the window the time in the "Created" field is the time it was when the "OK" button was pressed.

Expected Results:
When returning to the window the time in the "Created" field should be the time it was when pressing the "Reset Properties" button.


Reproducible: Always


User Profile Reset: No



Additional Info:
About LibreOffice info:
Version: 6.1.3.2 (x64)
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: en-US (en_US); Calc: CL
Comment 1 Oliver Brinzing 2018-11-18 17:51:19 UTC
already reproducible with OOo
Comment 2 QA Administrators 2019-11-19 03:28:52 UTC Comment hidden (obsolete)
Comment 3 Oliver Brinzing 2019-11-19 07:51:01 UTC
reproducible with:

Version: 6.5.0.0.alpha0+ (x64)
Build ID: d04eef858250f97690f32dba17f42d157a8767fc
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc: threaded
Comment 4 QA Administrators 2021-11-19 05:18:17 UTC
Dear Liad Skiva,

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