Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-13392

Due date not restricted to sensible year range

    XMLWordPrintable

Details

    Description

      Currently, some users are entering the due date invalidly as "01/Aug/7", this will be stored as "01/Aug/0007" in the database.

      The same string entered in a custom field date will result in an error: "Date too early. Dates must be after 1970".

      We should prevent users entering invalid dates like this by reusing the custom field date validation code's checks in our built-in date fields (eg. due date, version release dates, worklog dates).

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-10246 entry of date 0.jul.06 doesnt result in error

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-9141 Able to enter invalid date in Due Date field (Create new issue)

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-20007 Default date format is two-digit and loses century chosen in calendar picker

          • Low - Low priority issues
          • Gathering Impact

          Suggestion - JRASERVER-1375 Mandatory fields (aka custom validation)

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              lean.zhenyueh Zhen Yueh, Lean [Atlassian]
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: