Issue Summary
When comparing lastModified dates between the UI and API 2.0 response, some work item API response data show the time as UTC whereas others show as server time. For example, Defects lastModified will return UTC via the API whereas Capabilities returns server time (GMT-5 when testing against a US-based instance)
- Noticed also in lastUpdateDate on Epics/Features
Steps to Reproduce
- Run a simple GET against a defect, compare lastModified in the response to that in the Audit Log in the UI
- Do the same with a Capability
Expected Results
- PdM to confirm
- Timezone used for lastModified (or any time-date field for that matter) should be UTC
- This behavior should be consistent across all work items when accessed via the API
Actual Results
Timezone is inconsistent - the difference may be more pronounced when using a distant instance i.e. if you are in the US, try it on an APAC or EMEA-based instance and check the difference.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.
- relates to
-
JIRAALIGN-6090 API 2.0: Inconsistency With Date/Time When Item Is Created Via API And UI
-
- Closed
-
- resolves
-
ALIGNSP-7804 Loading...
-
ALIGNSP-8668 Loading...
-
ALIGNSP-9955 Loading...
-
ALIGNSP-13594 Loading...
-
ALIGNSP-14587 Loading...
-
ALIGNSP-21570 Loading...
-
ALIGNSP-22215 Loading...
-
ALIGNSP-23510 Loading...
-
PS-161186 Loading...
-
PS-162162 Loading...