Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-21994

Target Start and Target End custom fields behave as though they were a day behind when system timezone is set to negative offsets

    • 8.15
    • 12
    • Severity 3 - Minor
    • 50
    • Hide
      Atlassian Update – 27 Nov 2023

      Dear Customers,

      We're pleased to announce that we've resolved this issue in our 9.13 release.

      Before this fix, you may have experienced inconsistencies and confusion due to the different handling of dates in Advanced Roadmaps and other products in our suite. Advanced Roadmaps were storing and processing dates in UTC, while the rest of Jira was using them assuming they were in the system's timezone.

      We've addressed this by maintaining Advanced Roadmaps' storage of dates in UTC. However, these dates will now be converted from/to the system's timezone whenever data is requested or updated outside of the Advanced Roadmaps, such as in Jira issue details, issue history, issue search, Confluence macros, etc.

      To fully enjoy the benefits of this update and see the corrected time zones throughout Jira, we recommend reindexing the affected issues post-upgrade.

      Best regards,
      Daniel Rauf,
      Software Engineer

      Show
      Atlassian Update – 27 Nov 2023 Dear Customers, We're pleased to announce that we've resolved this issue in our 9.13 release. Before this fix, you may have experienced inconsistencies and confusion due to the different handling of dates in Advanced Roadmaps and other products in our suite. Advanced Roadmaps were storing and processing dates in UTC, while the rest of Jira was using them assuming they were in the system's timezone. We've addressed this by maintaining Advanced Roadmaps' storage of dates in UTC. However, these dates will now be converted from/to the system's timezone whenever data is requested or updated outside of the Advanced Roadmaps, such as in Jira issue details, issue history, issue search, Confluence macros, etc. To fully enjoy the benefits of this update and see the corrected time zones throughout Jira, we recommend reindexing the affected issues post-upgrade. Best regards, Daniel Rauf, Software Engineer

      Summary

      Jira issues may have a Target start and Target end date custom field. On Jira instances with the system time zone set to negative values, that is before GMT, when querying against these custom fields in the Issue Navigator using either Basic or Advanced search using JQL, these fields don't behave as expected when compared to Jira's own Date Picker and Date Time Picker custom fields.

      Specifically, issues behave as though their Target start and Target end values are a day behind their actual value. Put another way, issues are only returned in the Issue Navigator if queries that query against these two date fields successfully include a date range for the day prior to the actual value.

      The same problem appears in various places in Jira, not only in the issue search. Some examples include issue export, issue history, or Jira issue macros inside Confluence.

      There is a similar problem with a different root cause with the Due date field that you can follow here: https://jira.atlassian.com/browse/JRASERVER-73401

      Steps to Reproduce

      1. Start Jira with a system timezone with a "negative" timezone, for example, any timezone from the Americas
      2. Identify an issue which has either Target start or Target end set. For the sake of example, let's say that an issue has a Target start of 2018/03/15.
      3. In the issue navigator, attempt to search for this issue using any of the following JQL which we would expect would return the issue:
      • "Target start" >= '2018/03/15'
      • "Target start" = '2018/03/15'
      • "Target start" > '2018/03/14'

      Expected Results

      The issue in question would be returned in the results.

      Actual Results

      The issue is not returned in the results. The issue will only return for any of the following queries that would return as though the Target start was actually 2018/03/14.

      • "Target start" >= '2018/03/14'
      • "Target start" = '2018/03/14'
      • "Target start" <= '2018/03/14'

      Workaround

      Because the behavior is consistent in that the queries act as though the date were a day behind, JQL queries may safely be adjusted backward a day to compensate.

      Alternatively, you can re-start your Jira instance with a non-negative timezone (for example GMT) and re-index affected issues.

            [JSWSERVER-21994] Target Start and Target End custom fields behave as though they were a day behind when system timezone is set to negative offsets

            Kim Trask added a comment -

            Hi,

            We are running data center v 8.22.6 (Jira) and v 7.19.11 (Confluence). We have upgrades planned for both, but only plan to take Jira to 9.12 in the next jump. I have been wrestling with this issue also with Confluence's Jira Filter macro for "Start Date" and "End Date" fields. All dates are importing in Confluence as "-1" day. Does Jira 9.13 address these date fields as well?

            Thank you!

            Kim Trask added a comment - Hi, We are running data center v 8.22.6 (Jira) and v 7.19.11 (Confluence). We have upgrades planned for both, but only plan to take Jira to 9.12 in the next jump. I have been wrestling with this issue also with Confluence's Jira Filter macro for "Start Date" and "End Date" fields. All dates are importing in Confluence as "-1" day. Does Jira 9.13 address these date fields as well? Thank you!

            Atlassian Update – 27 Nov 2023

            Dear Customers,

            We're pleased to announce that we've resolved this issue in our 9.13 release.

            Before this fix, you may have experienced inconsistencies and confusion due to the different handling of dates in Advanced Roadmaps and other products in our suite. Advanced Roadmaps were storing and processing dates in UTC, while the rest of Jira was using them assuming they were in the system's timezone.

            We've addressed this by maintaining Advanced Roadmaps' storage of dates in UTC. However, these dates will now be converted from/to the system's timezone whenever data is requested or updated outside of the Advanced Roadmaps, such as in Jira issue details, issue history, issue search, Confluence macros, etc.

            To fully enjoy the benefits of this update and see the corrected time zones throughout Jira, we recommend reindexing the affected issues post-upgrade.

            Best regards,
            Daniel Rauf,
            Software Engineer

            Daniel Rauf added a comment - Atlassian Update – 27 Nov 2023 Dear Customers, We're pleased to announce that we've resolved this issue in our 9.13 release. Before this fix, you may have experienced inconsistencies and confusion due to the different handling of dates in Advanced Roadmaps and other products in our suite. Advanced Roadmaps were storing and processing dates in UTC, while the rest of Jira was using them assuming they were in the system's timezone. We've addressed this by maintaining Advanced Roadmaps' storage of dates in UTC. However, these dates will now be converted from/to the system's timezone whenever data is requested or updated outside of the Advanced Roadmaps, such as in Jira issue details, issue history, issue search, Confluence macros, etc. To fully enjoy the benefits of this update and see the corrected time zones throughout Jira, we recommend reindexing the affected issues post-upgrade. Best regards, Daniel Rauf, Software Engineer

            Stasiu added a comment -
            Atlassian Update – 25 September 2023

            Dear Customers,

            Thank you for taking the time to file and comment on this issue. We realize it still occurs and impacts your organization. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog. 

            The workaround for this bug is in the issue description.

            Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

            Best regards

            Daniel Dudziak
            Senior Software Engineer

            Stasiu added a comment - Atlassian Update – 25 September 2023 Dear Customers, Thank you for taking the time to file and comment on this issue. We realize it still occurs and impacts your organization. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog.  The workaround for this bug is in the issue description. Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards Daniel Dudziak Senior Software Engineer

            The underlying issue with Target Start and Target End date are tracked in https://jira.atlassian.com/browse/JPOSERVER-2358

            Please follow that issue for any further updates.

            Benjamin Morgan (Inactive) added a comment - The underlying issue with Target Start and Target End date are tracked in https://jira.atlassian.com/browse/JPOSERVER-2358 Please follow that issue for any further updates.

            Will Freeman added a comment - - edited

            Demoing functionality of the new advanced roadmaps and trying to get suitable reports and filters to align with the plans using these fields...

            They of course do not work, very surprised to see this issue open for more than 2 years.

            In addition to being wrong, I get "An unknown error occurred while trying to perform a search." attempting to use these fields in any filter, on the cloud version.

             

             

            Will Freeman added a comment - - edited Demoing functionality of the new advanced roadmaps and trying to get suitable reports and filters to align with the plans using these fields... They of course do not work, very surprised to see this issue open for more than 2 years. In addition to being wrong, I get "An unknown error occurred while trying to perform a search." attempting to use these fields in any filter, on the cloud version.    

            This is really causing confusion among our users. Please make this a priority!

            April Clark added a comment - This is really causing confusion among our users. Please make this a priority!

            CJ Henry added a comment -

            Confirmed this is happening in v3.1 as well.

            CJ Henry added a comment - Confirmed this is happening in v3.1 as well.

            I was pointed to this bug as I am seeing this behavior impacting other areas.

            1. Copying Target start/end to a custom date field in a workflow transition.
            2. Exporting from Issue Search
            3. REST API calls

            Eleanor Kauffman added a comment - I was pointed to this bug as I am seeing this behavior impacting other areas. Copying Target start/end to a custom date field in a workflow transition. Exporting from Issue Search REST API calls

              17c7584fdc03 Shushan Ulubabyan
              kliou Kevin Liou
              Affected customers:
              38 This affects my team
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: