-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.3.0
-
None
-
7.03
-
9
-
Severity 3 - Minor
-
0
-
Summary
Sprint End date disregards date picker advanced setting when duration is not custom
Steps to reproduce the problem
- 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
- Create a sprint > allocate issues
- 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
- Select "Custom" duration.
- In some cases, user will have to remove the AM or PM in the Start/End date.
- is related to
-
JSWSERVER-15344 Start Sprint date picker calendar disregards date picker advanced setting
-
- Gathering Impact
-
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.