Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-66986

Due date, Version dates or Date custom fields are showing up in a different timezone than the timezone in general configuration and user's profile

    XMLWordPrintable

Details

    Description

      2017-08-31 - Message from JIRA Cloud team

      Thank you to everyone for your patience whilst we work on this issue. We can now confirm that this problem should be resolved for JIRA Cloud customers.

      If you continue to experience this issue, or you are a customer experiencing this issue for the first time, please do get in touch with our Support team (getsupport.atlassian.com) to get the best assistance in remedying the problem.

      Thanks,
      JIRA Cloud team

      Summary

      When adding a value in the Due Date field, the user filled in the time expected in the timezone set in their profile. However, this date is converted to UTC and is perceived as the wrong date for the users of Jira.

      This occurs for Due dates on issues, Start & Release dates on versions, and Date-only custom fields on issues (not Date&Time custom fields).

      Environment

      JIRA Cloud

      Workaround

      Currently there is no workaround

      Attachments

        1. history.png
          history.png
          23 kB
        2. View screen.png
          View screen.png
          37 kB

        Issue Links

          Activity

            People

              ldurkan Skywalker
              nmuhi Nazri Muhi (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              26 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: