Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-42809

Epic Names and Version using JIRA Issue/Filter macro (in Confluence), cannot be displayed

XMLWordPrintable

      Hi team,

      Need your help in resolving the following bug asap. Any help would be much appreciated.

      Issue: I have a couple of epics and some stories associated with each of them in JIRA. When I created a wiki page in Confluence, I inserted some issues from JIRA using "JIRA Issue/Filter" built-in macro to display all the Epics and their respective stories in a table.
      While all the other attributes appear correctly I am not able to get to display, the names of the Epics in the table. I have included Epic Name and Epic Link both the columns, but Epic Name column in the table is empty, while Epic Link just populates the JIRA Id of the Epic in question.

      Ultimately, I need to display Epic Names in the table and not their ids. Please suggest how this could be fixed.

      Also, for your reference, please find the screen shot attached with the ticket

      Update

      This issue seems to also affect other fields like Version. When user generates a report; instead of showing the version number; it shows the version ID instead.

      For example. 

      jira=> select * from projectversion where id = 17718;
  id   | project | vname | description | sequence | released | archived | url | releasedate | startdate 
-------+---------+-------+-------------+----------+----------+----------+-----+-------------+-----------
 17718 |   11200 | 1.9   |             |       10 |          |          |     |             | 
(1 row)

      When a report is generated; instead of showing version 1.9 for an issue in a report; it shows 17718 instead.

        1. Confluence-JIRA Bug.docx
          234 kB
        2. insert jira dialog 2015-06-15 at 10.44.07 AM.png
          insert jira dialog 2015-06-15 at 10.44.07 AM.png
          86 kB
        3. jira issue example 2015-06-15 at 10.44.38 AM.png
          jira issue example 2015-06-15 at 10.44.38 AM.png
          15 kB
        4. Screen Shot 2015-06-16 at 12.09.45 AM.png
          Screen Shot 2015-06-16 at 12.09.45 AM.png
          188 kB
        5. Screen Shot 2015-06-16 at 12.10.03 AM.png
          Screen Shot 2015-06-16 at 12.10.03 AM.png
          146 kB
        6. Screen Shot 2015-06-16 at 2.03.23 AM.png
          Screen Shot 2015-06-16 at 2.03.23 AM.png
          154 kB
        7. Screen Shot 2015-08-10 at 2.18.05 PM.png
          Screen Shot 2015-08-10 at 2.18.05 PM.png
          118 kB

            [CONFSERVER-42809] Epic Names and Version using JIRA Issue/Filter macro (in Confluence), cannot be displayed

            Minh Tran added a comment -

            Dear rbray201091365975,

            Thanks for raising this issue. I believe this is something that our support team will be able to help you with.
            Could I ask that you create a support ticket on https://support.atlassian.com?
            Once you've done this one of our support engineers will be in touch to work with you in resolving this problem.

            Regards,
            Minh Tran
            Confluence Bugmaster
            Atlassian

            Minh Tran added a comment - Dear rbray201091365975 , Thanks for raising this issue. I believe this is something that our support team will be able to help you with. Could I ask that you create a support ticket on https://support.atlassian.com ? Once you've done this one of our support engineers will be in touch to work with you in resolving this problem. Regards, Minh Tran Confluence Bugmaster Atlassian

            Ryan Bray added a comment -

            Cloned CONF-36033 since we were not getting that bug re-opened. This issue still exists and needs to be fixed. IT IS NOT RESOLVED.

            Ryan Bray added a comment - Cloned CONF-36033 since we were not getting that bug re-opened. This issue still exists and needs to be fixed. IT IS NOT RESOLVED.

              Unassigned Unassigned
              5e1527fae6d0 Ryan Bray
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: