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

Assets Objects Date Attributes incorrectly recognize future dates after year 2030 as past century when entered via keyboard

XMLWordPrintable

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Navigate to any object type with date attribute or add a date attribute to an object type
      2. Enter a value for the date to be in the future past year 2030 eg. 2037-10-28
        • Note the date field accepts only 2 digits for year
        • Enter at least one digit using the keyboard

      Expected Results

      The date is recognized as 2037-10-28

      Actual Results

      The object is created with the value for that date being: 1937-10-10

      This will make all the AQL queries based on the date fail. See: https://jira.atlassian.com/browse/JSDSERVER-11990

      https://jira.atlassian.com/browse/JSDSERVER-8492

      https://jira.atlassian.com/browse/JSDSERVER-11030

      Workaround

      Set the date format in Jira to use YYYY for the year, see https://confluence.atlassian.com/adminjiraserver/configuring-the-look-and-feel-of-your-jira-applications-938846975.html

      Put 4-digit year in the field e.g. 01/Jan/2050

      OR

      Use the date picker to select the desired date with a mouse click.

      OR

      Use REST API to create objects with dates in the future -https://insight-javadoc.riada.io/assets-rest/#object_create_post-

            [JSDSERVER-12123] Assets Objects Date Attributes incorrectly recognize future dates after year 2030 as past century when entered via keyboard

            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.

            We found the issue even with API.

            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. We found the issue even with API. Please fix this! 

              Unassigned Unassigned
              bornatowski Bartosz Ornatowski
              Affected customers:
              4 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated: