NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      The data from Epic Link is not consistent with results retrieved from JIRA's Issue Navigator.

      In JIRA
      The Epic Link column in Issue Navigator will show the Epic Name

      In Confluence
      The Epic Name is not shown (as in JIRA) although we have set the same column Epic Link. Instead it shows the Epic ID.

      Workaround

      Add another JIRA Issue Macro to retrieve all epics, and include Epic Name column for reference in Confluence.

        1. conf_1.png
          conf_1.png
          27 kB
        2. conf_2.png
          conf_2.png
          34 kB
        3. epic.png
          epic.png
          24 kB
        4. jira.png
          jira.png
          37 kB
        5. version-picker-id.jpg
          version-picker-id.jpg
          71 kB

            [CONFSERVER-31339] Should show epic link in JIM (not epic id)

            Minh Tran added a comment -

            Dear All,

            This ticket has been marked as duplicate. Please follow the progress here https://jira.atlassian.com/browse/CONF-41537

            Thanks,
            Minh Tran
            Confluence BugMaster
            Atlassiano

            Minh Tran added a comment - Dear All, This ticket has been marked as duplicate. Please follow the progress here https://jira.atlassian.com/browse/CONF-41537 Thanks, Minh Tran Confluence BugMaster Atlassiano

            Hello,

            we are also affected from this BUG.

            Versions Used:
            Confluence: 5.9.12
            Jira: 7.1.8

            In our eyes this is not a "Suggestion" but a Bug.

            Please fix asap!

             

            Team Werkzeugunterstuetzung added a comment - - edited Hello, we are also affected from this BUG . Versions Used: Confluence: 5.9.12 Jira: 7.1.8 In our eyes this is not a "Suggestion" but a Bug. Please fix asap!  

            Guy Eden added a comment -

            Atlassian,

            I don't think this is being taken seriously enough. The issues here is entirely related to the comments at Ability to configure the maximum number of issues displayed in the JIRA issues macro.

            This macro is vital for many of us who genuinely use Jira and Confluence as an enterprise system. We depend on the ability to produce reports in Confluence based on Jira data.

            If I can't show the epic name next to a story, I lose vast amounts of value from the report.

            This is a bug not an improvement, and a major one - I would have hoped that following the comments at the above issue this would be obvious.

            Please fix it ASAP!

            Guy Eden added a comment - Atlassian, I don't think this is being taken seriously enough. The issues here is entirely related to the comments at Ability to configure the maximum number of issues displayed in the JIRA issues macro . This macro is vital for many of us who genuinely use Jira and Confluence as an enterprise system. We depend on the ability to produce reports in Confluence based on Jira data. If I can't show the epic name next to a story, I lose vast amounts of value from the report. This is a bug not an improvement, and a major one - I would have hoped that following the comments at the above issue this would be obvious. Please fix it ASAP!

            Stanislav Kralin added a comment - - edited

            Another workaround is to replace content of "Epic Link" column using AJAX request.
            Just wrap this code into "<script type =text/javascript>…</script>" and place the result into "HTML" macro:

            $.ajax({
                url: "https://example.com/jira/rest/greenhopper/1.0/epics?maxResults=100&projectKey=PRJ",
                type: 'get',
                dataType: 'json',
                async: true,
                error: function (e) {alert(e)} ,
                success: function(response) {
                    var keyvalue = response.epicNames.reduce (function (result,item) {
                        result[item.key] = item.name;
                        return result;
                        },
                    {}
                    );
                    $('table.aui').each(function(i, table) {
                        $(table).find("tr > th:contains('epic link')").each(function() {
                            var cellIndex = $(this).index() + 1;
                            $(table).find('tr > td:nth-child(' + cellIndex + ')').html ( function () {
                                var content = $(this).text().trim();
                                return '<a href = \'https://example.com/jira/browse/' + content  + '\'>' + ( content ? keyvalue[content] : '') + '</a>'
                            });
                        });
                    });
                }
            });
            

            It is possible to use this "HTML" macro not only in page with JIM output, but also in comments.

            Stanislav Kralin added a comment - - edited Another workaround is to replace content of "Epic Link" column using AJAX request. Just wrap this code into " <script type =text/javascript>…</script> " and place the result into "HTML" macro: $.ajax({ url: "https: //example.com/jira/rest/greenhopper/1.0/epics?maxResults=100&projectKey=PRJ" , type: 'get' , dataType: 'json' , async: true , error: function (e) {alert(e)} , success: function (response) { var keyvalue = response.epicNames.reduce ( function (result,item) { result[item.key] = item.name; return result; }, {} ); $( 'table.aui' ).each( function (i, table) { $(table).find( "tr > th:contains( 'epic link' )" ).each( function () { var cellIndex = $( this ).index() + 1; $(table).find( 'tr > td:nth-child(' + cellIndex + ')' ).html ( function () { var content = $( this ).text().trim(); return '<a href = \' https: //example.com/jira/browse/ ' + content + ' \ '>' + ( content ? keyvalue[content] : '') + ' </a>' }); }); }); } }); It is possible to use this "HTML" macro not only in page with JIM output, but also in comments.

            George Lewe (LSY) added a comment - - edited

            This bug affects all picker custom fields. See screenshot version-picker-id.jpg. "Target Version/s" is a custom field of type version pickler. Using it in a filter in JIRA shows the version name correctly. Anywhere in Confluence via the JIRA macro, the ID is shown instead.

            It is very annoying and I do not expect this to be big effort to fix. Probably just displaying a different field from an array. Can y please provide a fix for this?

            Update:
            Using Confluence 5.4.3 and JIRA Macros Plugin 5.4.5

            George Lewe (LSY) added a comment - - edited This bug affects all picker custom fields. See screenshot version-picker-id.jpg. "Target Version/s" is a custom field of type version pickler. Using it in a filter in JIRA shows the version name correctly. Anywhere in Confluence via the JIRA macro, the ID is shown instead. It is very annoying and I do not expect this to be big effort to fix. Probably just displaying a different field from an array. Can y please provide a fix for this? Update: Using Confluence 5.4.3 and JIRA Macros Plugin 5.4.5

            Jeff Kozloff added a comment - - edited

            Hello,
            I see the similar limitation. Thank you for the workaround in the meantime by creating a "legend" of sorts. Would be very helpful though if we could display the Epic Name and not just the number in the same table.

            Update
            I attempted this workaround, unfortunately when I try to two Macros on same page and I configure the columns to display, it affects the output of BOTH Macros. Here are the steps to reproduce:
            1. Add JIRA Issues Macro to page (first instance) and configure.
            2. Add another JIRA Issues Macro to the page (I used 2 column page layout, 1 macro in each column). Now when you configure the second Macro, you notice the display columns match the first macro. If you remove and add columns to display in Macro 2 and save it, you notice that Macro 1 updates as well.

            Using:

            • JIRA v6.1
            • Confluence 5.4.1

            Thank you,
            Jeff

            Jeff Kozloff added a comment - - edited Hello, I see the similar limitation. Thank you for the workaround in the meantime by creating a "legend" of sorts. Would be very helpful though if we could display the Epic Name and not just the number in the same table. Update I attempted this workaround, unfortunately when I try to two Macros on same page and I configure the columns to display, it affects the output of BOTH Macros. Here are the steps to reproduce: 1. Add JIRA Issues Macro to page (first instance) and configure. 2. Add another JIRA Issues Macro to the page (I used 2 column page layout, 1 macro in each column). Now when you configure the second Macro, you notice the display columns match the first macro. If you remove and add columns to display in Macro 2 and save it, you notice that Macro 1 updates as well. Using: JIRA v6.1 Confluence 5.4.1 Thank you, Jeff

              Unassigned Unassigned
              cchan Chung Park Chan
              Affected customers:
              30 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: