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

When Epic Link is chosen as a display field in the JIRA macro, it should show Epic Name.

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      This was recently fixed in Jira, where in Issue Navigator issues now show their Epic's name rather than the Epic's Issue Key.

      In Confluence, the Epic's Issue Key is still displayed when using the JIRA macro.

        1. image-2016-11-28-10-50-19-145.png
          image-2016-11-28-10-50-19-145.png
          5 kB

            [CONFSERVER-31534] When Epic Link is chosen as a display field in the JIRA macro, it should show Epic Name.

            Gaj Umapathy added a comment -

            From Atlassian.

            We actually have a more recent bug report for this issue at CONFSERVER-43561. This has already been fixed in Confluence 7.0.4 and we have submitted another internal request for this to be backported to confluence 6.13.x which is currently being reviewed by our development team.

            Gaj Umapathy added a comment - From Atlassian. We actually have a more recent bug report for this issue at  CONFSERVER-43561 . This has already been fixed in Confluence 7.0.4 and we have submitted another internal request for this to be backported to confluence 6.13.x which is currently being reviewed by our development team.

            Gaj Umapathy added a comment -

            I'm on Confluence 6.13.9 and Jira 8.5.3. This works intermittently without any admin changes. Before the Jira 8.5.3 we had the Epic link coming up just as a key when viewed in Confluence page but after the upgrade of Jira, it will show up the epic link in color just as we see in a Jira ticket. For some bizarre reason it stopped working for 24 hours and then started working again. I will log it with Atlassian but just want to mention here incase others are also having the same issue.

            Gaj Umapathy added a comment - I'm on Confluence 6.13.9 and Jira 8.5.3. This works intermittently without any admin changes. Before the Jira 8.5.3 we had the Epic link coming up just as a key when viewed in Confluence page but after the upgrade of Jira, it will show up the epic link in color just as we see in a Jira ticket. For some bizarre reason it stopped working for 24 hours and then started working again. I will log it with Atlassian but just want to mention here incase others are also having the same issue.

            Jean-François FORGET added a comment -

            Hi,

            Prod environment: Confluence 6.15.9 + Jira 8.3.2 ==> "Epic Link" field show epic ticket reference (wxas showing name previously)
            staging environment: Confluence 6.15.9 + Jira 8.3.2 ==> "Epic Link" field show epic name correctly

            Any idea about what can impact this behavior within same version?
            I can't see what action we made can lead to this.

            Jean-François FORGET added a comment - Hi, Prod environment: Confluence 6.15.9 + Jira 8.3.2 ==> "Epic Link" field show epic ticket reference (wxas showing name previously) staging environment: Confluence 6.15.9 + Jira 8.3.2 ==> "Epic Link" field show epic name correctly Any idea about what can impact this behavior within same version? I can't see what action we made can lead to this.

            Kent Rogers added a comment -

            FWIW, this works for us using Confluence 6.13.7 & Jira 7.13.1. I'm pretty sure it also worked with Confluence 6.13.6, which we were at for a very brief period of time.

            Kent Rogers added a comment - FWIW, this works for us using Confluence 6.13.7 & Jira 7.13.1. I'm pretty sure it also worked with Confluence 6.13.6, which we were at for a very brief period of time.

            Rob Purchase added a comment -

            We still have this issue in Confluence 6.15.9 / Jira 7.10.0.

            It should be re-opened and treated as a bug, since this has previously worked.

            Rob Purchase added a comment - We still have this issue in Confluence 6.15.9 / Jira 7.10.0. It should be re-opened and treated as a bug, since this has previously worked.

            Tom Van Rossom added a comment -

            Not fixed for Jira v7.13.5 and Confluence 6.13.6

            Tom Van Rossom added a comment - Not fixed for Jira v7.13.5 and Confluence 6.13.6

            Udo Carls added a comment -

            We have the same issue using Jira 7.13.0 and Confluence 6.10.1. Seeing the epic key is not very useful. Please fix this bug.

            Udo Carls added a comment - We have the same issue using Jira 7.13.0 and Confluence 6.10.1. Seeing the epic key is not very useful. Please fix this bug.

            Michael Hansen added a comment -

            We have this issue using  JIRA 8.0.2 and  Confluence 6.15.3

            In a brief period it worked, but now it is back to only showing the epic key instead of the epic name 

             

             

             

             

            Michael Hansen added a comment - We have this issue using  JIRA 8.0.2 and  Confluence 6.15.3 In a brief period it worked, but now it is back to only showing the epic key instead of the epic name         

            Kaarle Tukia added a comment -

            We have this issue in confluence 6.13.3 and Jira 7.9.2

             

            Kaarle Tukia added a comment - We have this issue in confluence 6.13.3 and Jira 7.9.2  

            Jonathan added a comment -

            it does work for me, running confluence 6.12.2

            Jonathan added a comment - it does work for me, running confluence 6.12.2

              rdelafuente@atlassian.com rupper (Inactive)
              ac2b61a228bc Adam Wong
              Votes:
              90 Vote for this issue
              Watchers:
              107 Start watching this issue

                Created:
                Updated:
                Resolved: