Defect #31986

Error selecting issues between dates after upgrading redmine 2.3.2 to 4.0.x

Added by Adauto Serpa almost 2 years ago. Updated almost 2 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Time tracking
Target version:-
Resolution: Affected version:4.0.4

Description

Hi,

I'm having problem to upgrade redmine 2.3.2 to 4.0.

After the Redmine update time entry reports do not bring the times entered on the corresponding dates.

Example Task list(dd/mm/yyyy):

Task 22572 executed on 01/07/2019
Task 22566 executed on 01/07/2019
Task 22204 executed on 01/07/2019
Task 22573 executed on 01/07/2019
Task 22584 executed on 02/07/2019
Task 18257 executed on 02/07/2019
Task 22585 executed on 02/07/2019
Task 22584 executed on 03/07/2019
Task 22117 executed on 03/07/2019
Task 22177 executed on 04/07/2019
Task 22584 executed on 04/07/2019

Selecting dates between 01/07/2019 and 03/07/2019
the result I have is(dd/mm/yyyy):

Task 22584 executed on 02/07/2019
Task 18257 executed on 02/07/2019
Task 22585 executed on 02/07/2019
Task 22584 executed on 03/07/2019
Task 22117 executed on 03/07/2019
Task 22177 executed on 04/07/2019
Task 22584 executed on 04/07/2019

As we can see redmine does not list the tasks of day 01 and lists the tasks of day 04 that should not be listed.
I suspected at first that it could be the database version, as it had migrated to MySQL version 8, but the problem persists in version 5.7.

To list the tasks of day 01 I have to specify the date of the day before 31.
Very strange this behavior of redmine.

If I create issues in a new database, Redmine behaves correctly.

Does anyone have any idea how or why this problem occurs?

rel_full_redmine.png - Complete task list (66.7 KB) Adauto Serpa, 2019-08-30 19:10

rel_redmine.png - Task list between dates (78.2 KB) Adauto Serpa, 2019-08-30 19:11

History

#1 Updated by Adauto Serpa almost 2 years ago

Adauto Serpa wrote:

Hi,

I'm having problem to upgrade redmine 2.3.2 to 4.0.

After the Redmine update time entry reports do not bring the times entered on the corresponding dates.

Example Task list(dd/mm/yyyy):

Task 22572 executed on 01/07/2019
Task 22566 executed on 01/07/2019
Task 22204 executed on 01/07/2019
Task 22573 executed on 01/07/2019
Task 22584 executed on 02/07/2019
Task 18257 executed on 02/07/2019
Task 22585 executed on 02/07/2019
Task 22584 executed on 03/07/2019
Task 22117 executed on 03/07/2019
Task 22177 executed on 04/07/2019
Task 22584 executed on 04/07/2019

Selecting dates between 01/07/2019 and 03/07/2019
the result I have is(dd/mm/yyyy):

Task 22584 executed on 02/07/2019
Task 18257 executed on 02/07/2019
Task 22585 executed on 02/07/2019
Task 22584 executed on 03/07/2019
Task 22117 executed on 03/07/2019
Task 22177 executed on 04/07/2019
Task 22584 executed on 04/07/2019

As we can see redmine does not list the tasks of day 01 and lists the tasks of day 04 that should not be listed.
I suspected at first that it could be the database version, as it had migrated to MySQL version 8, but the problem persists in version 5.7.

To list the tasks of day 01 I have to specify the date of the day before 31.
Very strange this behavior of redmine.

If I create issues in a new database, Redmine behaves correctly.

Does anyone have any idea how or why this problem occurs?

I tested with a normal Redmine installation and the bug did not occur. This bug is occurring in a docker installation.

Also available in: Atom PDF