-
Bug
-
Resolution: Fixed
-
Medium
-
5.5, 5.9.4, 6.6.8, 6.6.15, 6.15.1, 7.4.3, 7.4.8, 7.7.2, 7.13.7
-
27
-
Severity 2 - Major
-
39
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Summary
Jira Issues Macro is not displaying custom date fields in the user time zone (Confluence), but rather the server time zone (Confluence)
Environment
Confluence with applink to Jira
Steps to Reproduce
- In Jira, create a ticket with a custom date field and a custom date time field.
- Set the Jira user time zone to be different to the server time zone so that the custom fields display a different date.
- In Confluence, create a page with this issue and set the display option to table format with the custom fields.
- Set the Confluence user time zone to be the same as the Jira user time zone (assuming Confluence Server time zone is same as Jira).
Expected Results
Custom date and date time fields in Jira and Confluence display the same date and time.
Actual Results
Custom date and date time fields in Jira is displayed correctly according to user time zone settings while Confluence displays custom date and date time fields in Confluence Server time zone.
Custom date time fields can also be truncated to just the date and show the wrong date (in server time zone)
Notes
This behaviour is seen on both cloud and confluence server.
Jira rest endpoint is returning the custom date and custom date time fields in Jira user time zone eg <customfieldvalue>Wed, 20 Jul 2016 18:48:00 +0200</customfieldvalue>, JIM macro is incorrectly transforming this to Confluence server time zone instead of Confluence user time zone.
Workaround
none so far
- has a regression in
-
-
- Closed
-
- is related to
-
-
- Gathering Impact
-
- relates to
-
-
- Gathering Impact
-
- causes
-
PS-99579 You do not have permission to view this issue
[CONFSERVER-42863] Jira Issues Macro is not displaying custom date fields in the user time zone
| Affects Version/s | New: 7.13.7 [ 100900 ] |
| Comment | [ This is still occurring in server v8.22.6. ] |
| Link |
New:
This issue has a regression in |
| Remote Link | New: This issue links to "PS-99579 (Atlassian Support System)" [ 652389 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 7.16.2 [ 99701 ] |
| Fix Version/s | New: 7.17.0 [ 99301 ] | |
| QA Demo Status | New: Done [ 14331 ] | |
| QA Kickoff Status | New: Done [ 14235 ] | |
| Testing Notes |
New:
*STR:*
# Create a new task in Jira. Choose any Booking date. For example '14/Jan/22 11:29 AM' # Create a new page in Confluence and add Jira Issues Macro (JIM) there: ## Click '+' in menu toolbar and select 'Jira Issue/Filter' ## Search by issue key your issue ## Expand '{_}Display options{_}' ## Set '{_}Display as{_}' as '{_}Table{_}' ## Add your custom date filed name ('{_}Booking date{_}') to '{_}Columns to display{_}' list ## Click '{_}Insert{_}' and '{_}Publish{_}' *AR:* Custom date and date time fields in Jira is displayed correctly according to user time zone settings while Confluence displays custom date and date time fields in Confluence Server time zone. *ER:* Custom date and date time fields are formatting using Confluence user’s time zone {*}Other cases to test{*}: # Set Confluence user's preferred language to something other than default language of the Jira site and default language of the Confluence site. The date in Confluence must be localized using the Confluence user's preferred language. # Different regions may have different time offsets depending on the season of the year, so this may affect how many hours are added/subtracted in JIM. |
|
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| UIS | Original: 28 | New: 39 |
| UIS | Original: 37 | New: 28 |
| UIS | Original: 27 | New: 37 |