Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-53929

"Link to JIRA Epic" placeholder is missing when creating JIRA issues from Confluence

      Summary

      Link to JIRA Epic placeholder is missing when creating JIRA issues from Confluence using the Product Requirements Blueprint as per the documentation here:

      Environment

      • Confluence version 6.0.0-OD-2016.08.1-0001

      Steps to Reproduce

      1. Create a Confluence page using Product Requirements Blueprint
      2. Insert the link to any Epic in JIRA.
      3. Save the page.
      4. Highlight any text on the page and the create JIRA issue icon will appear. Click it.

      Expected Results

      The placeholder with a tickbox to link the issue being created to the Epic that is linked on the page will be visible.

      Actual Results

      The placeholder is missing as per the screenshot:

      Workaround

      Link the issues that are created manually in JIRA.

        1. epiclink.png
          epiclink.png
          35 kB
        2. in PUG.png
          in PUG.png
          52 kB
        3. screenshot-1.png
          screenshot-1.png
          52 kB
        4. Screen Shot 2016-05-27 at 1.24.56 PM.png
          Screen Shot 2016-05-27 at 1.24.56 PM.png
          33 kB
        5. Screen Shot 2016-05-27 at 1.25.30 PM.png
          Screen Shot 2016-05-27 at 1.25.30 PM.png
          172 kB
        6. Screen Shot 2016-05-27 at 1.25.47 PM.png
          Screen Shot 2016-05-27 at 1.25.47 PM.png
          170 kB

            [CONFCLOUD-53929] "Link to JIRA Epic" placeholder is missing when creating JIRA issues from Confluence

            This is definitely a must in confluence cloud. Would be nice if at least you change priority to 'medium'.

            Nahuel Moreno added a comment - This is definitely a must in confluence cloud. Would be nice if at least you change priority to 'medium'.

            Howard Ng added a comment -

            Howard Ng added a comment - Internal ticket: https://hello.atlassian.net/browse/CBT-1819

            Hi, until recently, multiple jira records we created from the confluence table were linked in the confluence table, but they are not currently linked. Can this be fixed as soon as possible please.

            Seda Gökhan added a comment - Hi, until recently, multiple jira records we created from the confluence table were linked in the confluence table, but they are not currently linked. Can this be fixed as soon as possible please.

            amahat added a comment -

            Hi any update on this issue? Can this be fixed as soon as possible please.

            amahat added a comment - Hi any update on this issue? Can this be fixed as soon as possible please.

            Hi is there any update on this. we need this fixed as soon as possible please 

            Sajid Faleel added a comment - Hi is there any update on this. we need this fixed as soon as possible please 

            We need a fix

            Niklas Kordasch added a comment - We need a fix

            Lars Fessler added a comment - - edited

            This ist not only a cloud issue but a datacenter issue as well. We miss this feature as well. It happens with a blank page as well, not only with a page created from Product Requirements Blueprint.

            We have staff who does not know their way around Jira that well. They need a straight forward way to properly epic link their issue while creating it. They are not able to search and bulk edit created issues. That would be too dangerous regarding other tickets which might get changed erroneously

            I hope this gets fixed soon!

            Lars Fessler added a comment - - edited This ist not only a cloud issue but a datacenter issue as well. We miss this feature as well. It happens with a blank page as well, not only with a page created from Product Requirements Blueprint. We have staff who does not know their way around Jira that well. They need a straight forward way to properly epic link their issue while creating it. They are not able to search and bulk edit created issues. That would be too dangerous regarding other tickets which might get changed erroneously I hope this gets fixed soon!

            this is a feature we're using heavily in our server version of Confluence and JIRA. Since Atlassian is forcing us to move to the cloud, I kind of expect this stuff to work properly...

            Gerben Heinen added a comment - this is a feature we're using heavily in our server version of Confluence and JIRA. Since Atlassian is forcing us to move to the cloud, I kind of expect this stuff to work properly...

            I'm also missing the epic linking when creating multiple tickets from a Confluence page. I can find them through a query, and bulk edit to add the epic but that is a waste of my time, esp when this used to work. I see it on YouTube videos working perfectly. Pls provide an update. Thank you.

            Laura Blom added a comment - I'm also missing the epic linking when creating multiple tickets from a Confluence page. I can find them through a query, and bulk edit to add the epic but that is a waste of my time, esp when this used to work. I see it on YouTube videos working perfectly. Pls provide an update. Thank you.

            This was working for us until about 3 weeks ago, when suddenly it stopped working. And what's funny is that we see the issue only happening when we try to create either EPIC or TASK to one specific team. When creating EPIC or TASK to another teams, it works just fine. So not sure if the bug is exactly the same but the behavior described originally in this page is the same. It is affecting our work productivity alot and this needs to be addressed asap. 

            Shiho Hashimoto added a comment - This was working for us until about 3 weeks ago, when suddenly it stopped working. And what's funny is that we see the issue only happening when we try to create either EPIC or TASK to one specific team. When creating EPIC or TASK to another teams, it works just fine. So not sure if the bug is exactly the same but the behavior described originally in this page is the same. It is affecting our work productivity alot and this needs to be addressed asap. 

              Unassigned Unassigned
              scranford Shawn C
              Affected customers:
              70 This affects my team
              Watchers:
              72 Start watching this issue

                Created:
                Updated: