プロジェクト

全般

プロフィール

Vote #80286

未完了

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

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Time tracking_13
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
13
version_id:
0
issue_org_id:
31986
author_id:
412290
assigned_to_id:
0
comments:
1
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
151
ステータス-->[New]

説明

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?


journals

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

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0