-
Bug
-
Resolution: Fixed
-
Low
-
None
-
4.3, 5.2.3
-
Tested against Confluence 4.3 integrated with JIRA 5.2.5
This issue is related to this bug: CONF-22154.
JIRA Issues Macro date formatting behaviour varies and here are the scenarios:
Scenario 1:
Confluence Date Format is set as: MMM dd, yyyy
The expected date format for JIRA Issues Macro should also be: MMM dd, yyyy
When renderMode is configured as "static", this setting is respected:
Scenario 2:
Confluence Date Format is set as: MMM dd, yyyy
The expected date format for JIRA Issues Macro should also be: MMM dd, yyyy
When renderMode is configured as "dynamic", this setting is NOT respected:
Scenario 3:
Confluence Date Format is set as: MMM dd, yyyy
The expected date format for JIRA Issues Macro should also be: MMM dd, yyyy
When renderMode is configured as "static" and columns are configured for example to "key,created,updated,resolved,summary" - Only "Created" date & "Updated" date followed Confluence Date Format while "Resolved" date do NOT:
Scenario 4:
Confluence Date Format is set as: MMM dd, yyyy
The expected date format for JIRA Issues Macro should also be: MMM dd, yyyy
When renderMode is configured as "dynamic" and columns are configured for example to "key,created,updated,resolved,summary" - None of the date format followed Confluence Date Format:
- is related to
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|