Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-8492

IQL Date function to search for objects with a past date returns date in future with year range 2042 to 9999

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 4.15.0, 4.16.0, 4.17.0, Mindville - Pre Bundled
    • Assets - Core experiences

      Issue Summary

      IQL Date function to search for objects with a past date returns date in future with year range 2042 to 9999

      Steps to Reproduce

      1. Create an object with a Date attribute.
      2. Set the value of the Date attribute to some date range 2042 to 9999. To make sure the year is registered as it is, enter the 4-digit year.
      3. Create another object with the date value in the past e.g. 12/12/2020
      4. After the creation of the objects, search with IQLs below with the attribute name replaced accordingly. 
        "Expire Date" < now()

"Expire Date" < -1d

      Expected Results

      The IQL is looking for objects with Expire Date in the past and hence, only the object with the past date (12/12/2020) in the result

      Actual Results

      Both objects show up in the result

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. image-2021-07-22-17-14-57-136.png
          image-2021-07-22-17-14-57-136.png
          38 kB

            [JSDSERVER-8492] IQL Date function to search for objects with a past date returns date in future with year range 2042 to 9999

            Olivier Adline added a comment -

            I have the same issue, that is impacting our organization !

            Olivier Adline added a comment - I have the same issue, that is impacting our organization !

            JIRA Supporto added a comment -

            +1 here too

            Is important to fix because the workaround couldn't be viable due to impacts on scripts and integrations

            JIRA Supporto added a comment - +1 here too Is important to fix because the workaround couldn't be viable due to impacts on scripts and integrations

            Roberto Martignano added a comment -

            +1 here.

            This is important because an Enterprise Customer of ours is using Insight to track expiration dates of Certificates, but it is not usable at the moment.

            Please fix this!

            Roberto Martignano added a comment - +1 here. This is important because an Enterprise Customer of ours is using Insight to track expiration dates of Certificates, but it is not usable at the moment. Please fix this!

            Tomasz Legutko added a comment -

            Hi, bumping this issue as for our company it's definitely not "Minor". We're using Insight to represent support contracts with our customers and we have condition based on start & end date that triggers SMS notifications to our support for Sev 1 incidents. Last week we almost broke SLA to our customer for whom we've had marked long date above 2042. Please fix this.

            Tomasz Legutko added a comment - Hi, bumping this issue as for our company it's definitely not "Minor". We're using Insight to represent support contracts with our customers and we have condition based on start & end date that triggers SMS notifications to our support for Sev 1 incidents. Last week we almost broke SLA to our customer for whom we've had marked long date above 2042. Please fix this.

              Unassigned Unassigned
              michin Michelle Chin
              Affected customers:
              8 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated: