Bug 41850 - Minimum and maximum are not always respected when validating time values.
Summary: Minimum and maximum are not always respected when validating time values.
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
3.4.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: target:3.5
Depends on:
Reported: 2011-10-16 16:38 UTC by Allan Jacobs
Modified: 2015-06-20 12:52 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Output after data detective has finished validating. (7.86 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-10-16 16:38 UTC, Allan Jacobs

Note You need to log in before you can comment on or make changes to this bug.
Description Allan Jacobs 2011-10-16 16:38:17 UTC
Created attachment 52401 [details]
Output after data detective has finished validating.

Enter data in a spreadsheet in range A1:A4
10:59:00 PM
11:59:00 PM
12:01:00 AM
01:00:00 AM

Select range A1:A4
Allow: Time
Minimum: 11:58:00 PM
Maximum: 12:02:00 AM
Tools->Detective-Mark Invalid Data

11:59:00 PM and 12:01:00 AM are marked invalid.  10:59:00 PM and 01:00:00 AM are regarded as valid.  This is the reverse of the true situation.
Comment 1 Markus Mohrhard 2011-10-17 09:43:34 UTC
Ok, I think I know why that happens.

We need to take care of Between and Not Between with time and dates in a different way than we do now. We translate the date to a double value and sort them after that and look if that value is between these two. Since 11:59 PM is bigger than 12:01 AM we inverse our valid range.

I think about a clean way to fix that.
Comment 3 retired 2013-12-08 12:18:10 UTC
Markus: I'm freeing this bug. Just re-assign if you still plan on working on this.
Comment 4 bfoman (inactive) 2014-01-08 22:40:40 UTC
Back to NEW as this bug lost owner.
Comment 5 Joel Madero 2015-05-02 15:41:20 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.4.2 or later)

   If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)


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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Comment 6 Buovjaga 2015-06-20 12:52:37 UTC
Could not reproduce from scratch. WFM.

Win 7 Pro 64-bit Version:
Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58
Locale: fi-FI (fi_FI)