Bug 127641

Summary: Delay in days in Date field shouldn't be limited to 31 days backwards/forwards
Product: LibreOffice Reporter: Mathias <tiax>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: enhancement    
Priority: medium    
Version: 6.3.1.2 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 107739    

Description Mathias 2019-09-19 10:15:25 UTC
Description:
It isn't possible any more to put a higher value than +/-31 days in the input field to get a different date in relation to today.

For example: if I want to display the last year from now (2018) I use -365 (delay in days) or -730 to make it display 2017

Steps to Reproduce:
1. insert
2. field 
3. date
4. double click field for settings
5. lower or rise value above 31

Actual Results:
A maximum of 31 days from now are calculated.

Expected Results:
Every date from now should be possible to be calculated


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Roman Kuznetsov 2019-09-20 13:55:45 UTC
confirm in

Version: 6.4.0.0.alpha0+ (x64)
Build ID: 06925c1230cd6269fa5189ac3f4d608c9edf68e9
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-09-17_00:45:28
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

I think it's an enhancement
Comment 2 Mike Kaganski 2019-10-27 16:22:37 UTC
(In reply to Roman Kuznetsov from comment #1)
> I think it's an enhancement

I suspect a regression: https://ask.libreoffice.org/en/question/214761/lo-writer-id-like-to-shift-the-field-inserted-date-more-than-31-days/
Comment 3 Mike Kaganski 2019-10-27 16:28:36 UTC
And actually I cannot reproduce with Version: 6.3.3.2 (x64)
Build ID: a64200df03143b798afd1ec74a12ab50359878ed
CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded
Comment 4 Mike Kaganski 2019-10-27 16:43:17 UTC

*** This bug has been marked as a duplicate of bug 127840 ***