Summary

Epic Link column in "Insert JIRA Issue/Filter" (a table inserted in a Confluence page) does not have an hyperlink to the corresponding Epic. Additionally, this field in Confluence does not show the name of the Epic (as Jira's equivalent column does), and does not color-code the Epic link.

Steps to Reproduce

Pre-requisites:

• Confluence and Jira have an Application Link established and working
• In Jira there is at least one existing issue (FLP-7, bug1) which is linked to an Epic (e.g. FLP-2 with Epic name "CSP-183740 test") in the same project (FLP)

Steps:

1. Create a new page in Confluence and write a title
2. Insert "JIRA Issue/Filter"
3. Write a filter to grab all the issues from project FLP
4. Open the "Display Options" and edit the columns to be show to be
   • Key
   • Summary
   • Epic Link
   • Epic Name
5. Click "Insert" and save the Confluence Page...

Now navigate to Jira and search for issues:

1. Issues > Search For Issues > write a filter for 'project = "FLP"'
2. Configure the Columns of this query to show:
   • Key
   • Summary
   • Epic Link
   • Epic Name
3. Now observe the generated table and compare it to the one created in Confluence through Jira filter macro.

Expected Results

By comparing both tables, we observe that the columns in Confluence do not match the columns in Jira. There are several issues:

1. The epic link should be a link in Confluence
2. The epic link should also show the name of the Epic, to conform to what is seen in Jira
3. The epic link should also be color coded, as in Jira.

Actual Results

1. The Epic Link is not a link in Confluence. The field name implies that it should be a link to the Epic.
2. The Epic Link in Jira shows the Epic name, while in Confluence it shows the Key of the corresponding issue
3. The Epic Link in Confluence is not color coded as it is in Jira.

The screenshot below shows the difference between the same filter configured in Jira and Confluence:

Notes

The issue is not always reproducible, on several cases it happens intermittently.

Workaround

There is no workaround. The users have to manually lookup for the issue key corresponding to the Epic they are looking for. There is no known way to display the information as neatly as it is in Jira.