Target start and target end dates are not properly reflecting the dates when using any "negative" timezone in relation to UTC

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 9
    • Severity 3 - Minor

      When creating an issue in Advanced Roadmaps and populating Target start and Target end date fields, the stored dates fetched through the REST API are not all correct.

      For instance, when you create an Epic and set:

      • Due Date (System Field)
      • Target start (ARJ field)
      • Target end (ARJ field); and
      • myCustomDateField (custom Date picker field)

      to today (2021/12/21), the issue view shows:

      Due Date:	21/Dec/21
      Target start:	21/Dec/21
      Target end:	21/Dec/21
      myCustomDateField:	21/Dec/21

       

      When using a -0300 TZ for Jira, the rest/api/latest/issue/BS-5 shows:

      duedate: "2021-12-21",
      customfield_10101: "2021-12-20", --Target start
      customfield_10102: "2021-12-20", --Target end
      customfield_10300: "2021-12-21", --myCustomDateField
      

       

      When the Jira system TZ is changed to UTC +1, the dates are all correct:

      duedate: "2021-12-21",
      customfield_10101: "2021-12-21", --Target start
      customfield_10102: "2021-12-21", --Target end
      customfield_10300: "2021-12-21", --myCustomDateField

            Assignee:
            Dong
            Reporter:
            Quentin Feyaerts
            Archiver:
            Aakrity Tibrewal

              Created:
              Updated:
              Resolved:
              Archived: