-
Bug
-
Resolution: Fixed
-
Low
-
6.6.5, 6.8.0
-
6
-
Severity 2 - Major
-
1
-
Summary
Jira Issue Table with 'Epic Link' column will take much longer to render compared to a table that doesn't have 'Epic Link' column in it.
Environment
Tested on Confluence 6.8 + Jira Software 7.8
Steps to Replicate
- Create a test project in Jira (eg. TEST)
- Create ~1000 Jira Issue in Jira with Epic Link in TEST
- In Confluence, insert a Jira Issue Macro with project=TEST as the search filter
- Include "Epic Link" in the Columns to display option
- Set Maximum issues to 1000
- Insert
- Observe the amount of time taken to load the table
- Edit the Jira Issue Macro and remove "Epic Link" in the Columns to display option (leave the rest as it is)
- Insert
- Observe the amount of time taken to load the table again
Expected Behavior
The table loads quickly with or without "Epic Link" column
Actual Behavior
According to test results, it took ~2 seconds for the table to populate without Epic Link. On the other hand, it took ~15 seconds for the table to populate with Epic Link.
| Condition | Load Time | HAR File |
|---|---|---|
| With "Epic Link" | ~15 seconds | with epic link.har |
| Without "Epic Link" | ~2 seconds | without epic link.har |
Note
- Jira Issue Macro starts showing notable slowness while Maximum issues is set to 500 or above.
- If Confluence took longer than the expected timeframe, you'll notice the following message:
- The same issue is also observed when 'Epic Name' column is added to the filter as well.
Workaround
- Increase socket timeout as suggested in Timeouts in the JIRA Issues Macro or Highlighting Plugin
- Lower the amount of issue display in the table.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-55926] 'Epic Link' column causes longer load time for Jira Issue Macro
Jira should provide a field with the epic name without the link, that should solve the issue for the majority of users
A fix for this issue is available to Server and Data Center customers in Confluence 7.15 Upgrade now or check out the Release Notes to see what other issues are resolved.
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Status | Original: Awaiting Merge [ 10064 ] | New: Waiting for Release [ 12075 ] |
| QA Demo Status | Original: Not Done [ 14330 ] | New: Done [ 14331 ] |
| Status | Original: In Review [ 10051 ] | New: Awaiting Merge [ 10064 ] |
| QA Kickoff Status | Original: Not Done [ 14234 ] | New: Done [ 14235 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10051 ] |
| Status | Original: Long Term Backlog [ 12073 ] | New: In Progress [ 3 ] |
| Fix Version/s | New: 7.15.0 [ 97722 ] |
| Testing Notes |
Original:
* WHW with no EPIC columns info
* WHW with all ticket belong to single EPIC columns info * WHW tickets belong to multiple EPIC * WHW with no custom field but have EPIC columns info * WHW with custom field and have EPIC column info |
New:
* WHW with no EPIC info is contained in xml result (/)
* WHW with no EPIC columns info (/) * WHW with all ticket belong to single EPIC columns info (/) * WHW tickets belong to multiple EPIC (/) * WHW with no custom field but have EPIC columns info (/) * WHW with custom field and have EPIC column info (/) |
We are on 7.19 and are still impacted by this bug. Jira is running 9.4.3.