-
Bug
-
Resolution: Fixed
-
Low
-
10.0.0, 5.17.0, 10.2.0, 10.1.1, 10.3.2
-
2
-
Severity 2 - Major
-
12
-
Issue Summary
On JSM 10.x, Assets postfunction "Create an Assets Object from a Jira Issue" cannot handle "dd.MM.yyyy HH:mm" datetime format if the date (dd) value is less than or equal to 12.
This is reproducible on Data Center: yes
Steps to Reproduce
Due to the nature of the bug, this seems to be happening for any date/dateTime format with digit month value "MM" instead of the abbr. alphabetical month "MMM".
1. Set up Look and feel:
| Time Format | HH:mm |
|---|---|
| Day Format | EEEE HH:mm |
| Complete Date/Time Format | dd.MM.yyyy HH:mm |
| Day/Month/Year Format | dd.MM.yyyy |
2. Set the following date/datetime picker format in System > General Configuration > Advanced Settings:
| Key | Value |
|---|---|
| jira.date.picker.java.format | dd.MM.yyyy |
| jira.date.picker.javascript.format | %d.%m.%Y |
| jira.date.time.picker.java.format | dd.MM.yyyy HH:mm |
| jira.date.time.picker.javascript.format | %d.%m.%Y %H:%M |
3. Create one/two Date Time Picker custom fields and apply to applicable screens:
4. Add DateTime attribute in any object type:
5. Add an Assets workflow post-function “Create an Assets Object from a Jira Issue“ and map the date time picker Custom Fields with the datetime attribute of the object type:
6. Transition a Jira issue to trigger the post-function after populating the date time picker CFs with a day value less than 12:
7. Transition another Jira issue to trigger the post-function after populating the date time picker CFs with a day value more than 12
Expected Results
The created Assets object from the post-function is able to handle both dates correctly
Actual Results
| Day value less than 12 | Day value more than 12 |
|---|---|
 |
 |
The same is reflected in the database as well:
Workaround
Use the default datetime picker
- is related to
-
-
- Closed
-
- links to
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|