Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-2358

Bug: Target Start and Target End fields store incorrect values in CEST within jira create rest calls

    XMLWordPrintable

    Details

      Description

      Atlassian Update – 14 October 2020

      Hi everyone,

      Thank you for your interest in this issue.

      We have investigated this issue and the underlying problem is the handling of dates and timezones within Jira. This bug for target start and due date is one of several examples of the underlying problem.

      We would not be able to address the problem independently and addressing the problem completely in the product would require a significant investment. Unfortunately, it's not high on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will keep the issue open and continue to watch this issue for the further updates.

      Kind regards,
      Ben Morgan, Jira Engineering Manager

      Environment
      OS Ubuntu Server 16.04, Jira Software 7.1.10 , jdk 1.8.0_171-b11, Portfolio 2.13.1
      OS Windows 10, Jira Software 7.10.1, jdk 1.8.0_172, Portfolio 2.13.3

      Steps to Reproduce

      • Start Jira and add the Due date, Target Start (e.g. customfield_10109), Target End (e.g. customfield_1011) fields to the create issue screen (e.g. for Epics)
      • Shutdown Jira
      • Set the timezone of the OS to UTC
      • Start Jira
      • Create an Epic using the rest interface of jira http://SERVER/rest/api/2/issue (POST)
        {
           "fields":{
              "project":{
                 "key":"TP"
              },
              "issuetype":{
                 "name":"Epic"
              },
              "summary":"Some Epic",
              "duedate":"2018-03-03",
              "customfield_10104":"Some Epic",
              "customfield_10109":"2018-02-02",
              "customfield_10110":"2018-03-03"
           }
        }
        
      • Issue will have the following values:
        • Target start 2018-02-02
        • Target end 2018-03-03
        • Due date 2018-03-03
      • Shutdown Jira
      • Set the timezone of the OS to CEST
      • Start Jira
      • Create an Epic using the rest interface of jira http://SERVER/rest/api/2/issue (POST)
        {
           "fields":{
              "project":{
                 "key":"TP"
              },
              "issuetype":{
                 "name":"Epic"
              },
              "summary":"Some Epic",
              "duedate":"2018-03-03",
              "customfield_10104":"Some Epic",
              "customfield_10109":"2018-02-02",
              "customfield_10110":"2018-03-03"
           }
        }
        
      • Issue will have the following values:
        • Target start 2018-02-01
        • Target end 2018-03-02
        • Due date 2018-03-03

      Expected Results
      The time zone of the operating system should not cause any problems.

      Actual Results
      One day is deducted from the Target start / Target end fields.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              spall1 Andreas Spall (evolu.software)
              Votes:
              30 Vote for this issue
              Watchers:
              39 Start watching this issue

                Dates

                Created:
                Updated: