Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2767

API 2.0: lastModified/lastUpdatedDate Timezone Inconsistency

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 10.132.0
    • 10.85, 10.86, 10.87, 10.88, 10.89, 10.90, 10.127.2
    • REST API
    • 10
    • Severity 3 - Minor
    • No

    Description

      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

      1. Run a simple GET against a defect, compare lastModified in the response to that in the Audit Log in the UI
      2. 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.

      Attachments

        Issue Links

          Activity

            People

              kforeman@atlassian.com Kyle Foreman
              fd18f17e9ccb align-connector-bot
              Votes:
              8 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync