Tech Debt: All date time fields should always be in epoch time and milliseconds.

[subhashini-egov]

Describe the bug All date time fields to be in epoch time across all services. The API specs reflect that. UI should pass values to the API in epoch. UI should also format from epoch ms and display appropriately.

To Reproduce

1. Follow steps to e-file a case.
2. Open the network tab of the developer console in Chrome. Or if using some other browser, use appropriate developer tools.
3. Monitor the payload being sent for the "create" API for the case service. Check the filingDate and registrationDate attributes in the request/response payloads

Expected behavior

Filing date, registration date etc.. in both request and response payloads should be in epoch time (ms) - not in human readable format.

Screenshots

Desktop (please complete the following information):

• OS: MacOS
• Chrome
• Version 126.0.6478.62 (Official Build) (arm64)

Additional context

While this example has been given specific to case e-filing, this is applicable across all services.

[subhashini-egov]

@anirudh-0 is this already fixed? I had forgotten to add the showstopper label. If fixed, please do close. Else, please address.

[Ramu-kandimalla]

Please verify and confirm @rajeshcherukumalli

[Beehyv-Vinod]

Hi @Ramu-kandimalla @rajeshcherukumalli Tested in QA, Working fine.

1. When we create the case, filingDate showing as epoch time in update API
2. When we Register the case by Judge, both "filingDate" & "registrationDate" showing as epoch time in Update API
3. When we search the specific case, In Search API "filingDate" & "registrationDate" showing as epoch time