Next date issue in WM

[jmgasper]

@suppermancool - Reported by QA:

I observed that synching is not happening in WM for auto-copilot (where the phases closes by itself), the time it closes is displayed correctly in OR but it is not changing in WM

Note: The changes we made in WM as well as OR are synching fine

Sample 1

sample: View Details (topcoder-dev.com)

Sample 2

sample: View Details (topcoder-dev.com)

[suppermancool]

@jmgasper the backend returns the inconsistent data For sample 1: backend response for registration phase

...
phases: [
...
{
{
      "duration": 3600,
      "scheduledEndDate": "2023-04-19T05:21:02.000Z",
      "actualEndDate": "2023-04-19T05:21:02.000Z",
      "isOpen": false,
      "name": "Registration",
      "phaseId": "a93544bc-c165-4af4-b55e-18f3593b457a",
      "actualStartDate": "2023-04-19T04:18:35.000Z",
      "description": "Registration Phase",
      "id": "1c35bd31-49d2-422a-8fe6-48807be749e1",
      "constraints": [{ "name": "Number of Registrants", "value": 1 }],
      "scheduledStartDate": "2023-04-19T04:18:35.000Z"
    }
}
...
]
...

Duration = 3600 seconds => Hour:1 Minutes: 0 (This duration is used in WM) but scheduledEndDate-scheduledStartDate = 63 minutes => Hour:1 Minutes: 3 (This duration matches with OR)

How to know which Duration need to use?

[suppermancool]

@jmgasper ignore this. i check wrong phase

[jmgasper]

@suppermancool - Let's change this to use the same display as OR, as long as we aren't changing the fields that should be fine.

[suppermancool]

Done in work-manager-issue-1521.patch (develop branch) Best regards,

Diazz.

On Fri, Apr 21, 2023 at 6:03 AM Justin Gasper @.***> wrote:

@suppermancool https://github.com/suppermancool - Let's change this to use the same display as OR, as long as we aren't changing the fields that should be fine.

— Reply to this email directly, view it on GitHub https://github.com/topcoder-platform/work-manager/issues/1521#issuecomment-1517041155, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMLXDTHUHYWVWLFZKVPKZLXCG6CPANCNFSM6AAAAAAXEYF2GI . You are receiving this because you were mentioned.Message ID: @.***>