Bug 149463

Summary: Calc/Graph/trend curve format, if type moving average, type is not saved with document, always after reopening is set to preceeding
Product: LibreOffice Reporter: Miro <miro.magula>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: minor CC: miguelangelrv
Priority: medium    
Version: 7.2.7.2 release   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Miro 2022-06-05 20:35:17 UTC
Description:
Calc/Graph/trend curve format, if type moving average, type is not saved with document, always after reopening is set to preceeding, disregarding changing to other type before saving.

Steps to Reproduce:
1.Add graph, trebd curve moving average, change type from preceeding to middle.
2.Save document.
3.After reopening, trend curve type is preceeding again instead of middle.

Actual Results:
Not all the trend curve properties are saved with document.

Expected Results:
3.After reopening, trend curve type is preceeding again instead of middle.


Reproducible: Always


User Profile Reset: No



Additional Info:
Trend curve type ought to be saved as it was selected.
Comment 1 m_a_riosv 2022-06-06 18:36:15 UTC
Please attach a sample file, with the file format you used to save it.
Comment 2 QA Administrators 2022-12-04 03:52:06 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2023-01-04 03:19:34 UTC
Dear Miro,

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-FollowUp