-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.1.2, 7.2.2, 7.3.3
-
None
-
15
-
Severity 3 - Minor
-
5
-
Issue Summary
Similar to the following closed issue: CONFSERVER-43561: Epic Link column in Confluence's "Insert JIRA Issue/Filter" is not displayed properly (fixed in Confluence Server 7.0.4)
Jira issue filter does not show the Epic link and name if the page was directly accessed prior to being authenticated. This is specific to each individual Jira issue filter and different filters are not affected across separate pages.
Steps to Reproduce
Pre-requisites:
- Confluence and Jira have an Application Link established and working.
- Versions tested:
- Confluence 7.1.2, 7.2.2, 7.3.3
- Jira 7.13.4, 8.3.4
- Versions tested:
- In Jira, there is at least one existing issue which is linked to an Epic in the same project.
Steps:
- Create a new page in Confluence and write a title
- Insert "JIRA Issue/Filter"
- Write a filter to grab all the issues from project FLP
- Open the "Display Options" and edit the columns to be shown:
- Key
- Summary
- Epic Link
- Epic Name
- Click "Insert" and save the Confluence Page...
- Restart Confluence
- Access the page using the direct link(Example: http(s)://[hostname]:[port]/display/TEST/Jira+issues+2)
- Authenticate to the page to view the filter
- The Jira issue filter does not show the Epic link and name. It also is not hyperlinked.
Expected Results
- The epic link should be a link in Confluence
- The epic link should also show the name of the Epic, to conform to what is seen in Jira
- The epic link should also be color-coded, as in Jira.
Actual Results
- The Epic Link is not a link in Confluence. The field name implies that it should be a link to the Epic.
- The Epic Link in Jira shows the Epic name, while in Confluence it shows the Key of the corresponding issue
- The Epic Link in Confluence is not color-coded as it is in Jira.
The following image shows the differences:
Workaround
Restarting Confluence and accessing the page after authentication appears to correct the behavior.
(this workaround doesn’t work 100% of times, sometimes it shows correct value and later shows the same behavior)