-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Product - Admin Logs, REST API
-
None
-
1
Business use-case:
Create a Capability via API or UI including "portfolioAskDate", "startInitiationDate", and "targetCompletionDate".
For example, created a Capability via API (POST) using the below body from client computer in IST (UTC +5:30):
{
"title":"Capability via API - API audit log testing case",
"primaryProgramId":617,
"parentId":7659,
"description":"Capability via API - API audit log testing case",
"type":1,
"state":1,
"targetCompletionDate":"2024-07-31 03:15:00 PM",
"startInitiationDate":"2024-07-22 02:45:00 AM",
"portfolioAskDate":"2024-07-31 01:30:00 PM"
}
POST has taken the values as UTC irrespective of client computer time. Z=Zero (UTC+0)
The GET output for capability shows the time date/time based on UTC+0 (Z=Zero)
"targetCompletionDate": "2024-07-31T15:15:00.000Z", "startInitiationDate":"2024-07-22T02:45:00.000Z", "portfolioAskDate":"2024-07-31T13:30:00.000Z",
However, the GET output of /audit log shows the time in server time UTC-4:
<font class='fields'>Target Completion</font>: <font class='values'>7/31/2024 11:15:00 AM</font></li><li><font class='fields'>Start / Initiation</font>: <font class='values'>7/21/2024 10:45:00 PM</font></li><li><font class='fields'>Portfolio Ask</font>: <font class='values'>7/31/2024 9:30:00 AM</font>
Business-Impact:
Parsing output of what workitems have been modified and when relying on GET /auditlog/<ID> and validating with value from GET /<workitem_type/<ID> does not match
Suggestion request:
Display timestamps of GET API /auditlog/id output in UTC+0 (Z)