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

Sprint End date disregards date picker advanced setting when duration is not custom

XMLWordPrintable

      Summary

      Sprint End date disregards date picker advanced setting when duration is not custom

      Steps to reproduce the problem

      1. Configure advanced configuration datepicker as follow:
        • jira.date.time.picker.java.format : dd.MM.yyyy HH:mm
        • jira.date.time.picker.javascript.format : %d.%m.%y %I:%M
      2. Create a sprint > allocate issues
      3. Start sprint > choose duration of 1 week (any option other than custom)

      Expected Result

      Date picker will show the date following the advanced configuration

      Actual Result

      Date picker does not follow the date picker format

      This problem does not happen if user choose custom duration as default:

      If the user chooses non-custom duration initially, and then switch back to custom, the end date will still show the wrong format of the year.

       

      Workaround

      1. Select "Custom" duration.
      2. In some cases, user will have to remove the AM or PM in the Start/End date.

        1. custom.png
          142 kB
        2. image-2017-04-14-16-24-48-363.png
          44 kB
        3. image-2017-04-14-16-32-16-743.png
          50 kB
        4. notcustom.png
          140 kB

            [JSWSERVER-15811] Sprint End date disregards date picker advanced setting when duration is not custom

            SET Analytics Bot made changes -
            Support reference count Original: 8 New: 9
            SET Analytics Bot made changes -
            Support reference count Original: 7 New: 8
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            UIS New: 1
            Bugfix Automation Bot made changes -
            Support reference count Original: 6 New: 7

            Richard Bone added a comment - - edited

            Workaround is to create the sprint using the custom option and set it for 11 days so the end date is on a Saturday and only uses 10 working days. 

             

            Richard Bone added a comment - - edited Workaround is to create the sprint using the custom option and set it for 11 days so the end date is on a Saturday and only uses 10 working days.   
            Bugfix Automation Bot made changes -
            Support reference count Original: 5 New: 6
            Bugfix Automation Bot made changes -
            Support reference count Original: 4 New: 5
            Bugfix Automation Bot made changes -
            Minimum Version New: 7.03
            Bugfix Automation Bot made changes -
            Support reference count Original: 3 New: 4

              Unassigned Unassigned
              azuhra Aqqiela
              Affected customers:
              9 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: