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

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.

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

We need a fix

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...

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. 

I was just checking the history of this ticket, was it really raised back in 2016? 

I wonder how long this takes before Atlassian fixes it. It affects anybody that uses confluence cloud, not just the people who have taken the time to say they are affected. As Atlassian are moving people from on-premise to cloud this number will only increase. It's been documented for well over 2 years now, probably longer, and the engineering team , take the time to add header images to pages, which we could all do anyway by adding images ourselves. Is anyone from Atlassian listening? Who is the product manager, this is a core feature of the product we all use as part of our workflow. Just crazy.

Hi, it looks like there hasn't been much progress on this bug. This has been a huge issue for my team and myself. Would love some updates.

Just like Andéas' comment above, we ran in to this almost immediately when setting up Confluence + Jira.

The goal is to have:

Product requirements template = Epic
Requirements within the template = Tasks belonging to that Epic

I didn't create multiple epics on the page or anything, so I'm a bit baffled. This seems like the intended behavior / relationship but I'm struggling to make it work due to this bug.

Am I missing something?

I was using this feature very intensively, since I relied on Confluence for all the documentation and then this feature gave me the ability to create issues directly. However with this issue, the feature is of no longer help, since I manually have to add EPICs in JIRA, which defeats the purpose of using the feature. 

Wonder when will this get fixed. 

We just recently started using Confluence Cloud (with Jira Cloud) and literally within 5 minutes I stumbled upon this bug. I agree with some of the comments above that this is right on the path of our envisioned workflow and would greatly appreciate having it fixed.

I can add that I did a test with a blank page where I created a single new epic in Jira. Then the dialog works as expected. I could add new Stories and they were linked to the correct Epic i Jira. I then created a second Epic on the same page and it stopped working. I deleted the second link and it still doesn't work. So now my page became a lot less useful than before.

 I was able to reproduce the issue and was able to get the Link to Epic to "reappear" also. In the new Confluence editor, the Epic that is added is within a table within the Page Properties macro. When I remove it from the table and just added the Epic directly in the Page Properties (Details), the Link to Epic appears to now recognize the Epic to link to.

Hi, 

This feature is also required for our work. Could you please advise how to solve it so we won't need to connect the tickets manually?

Thanks!

Hi, there!

Creating tickets out of Confluence is our main development path for transforming requirement documents into actual Jira issues. Currently, we are introducing the Atlassian tool chain to the whole company, and the need to transform requirement tables into Jira issues is growing on a daily basis.
As you can imagine, this bug creates a lot of additional work and I am a little bit distressed about it.

I understand, that there is a workaround to link all tickets manually. However, this takes a lot of time. Furthermore, it introduces an additional source of errors to our working process. I'd like to reduce that.

In case there is any possiblity to speed up the fixing of this ticket, this would be great and highly appreciated.

Along with this bug, we've also been experiencing CONFCLOUD-57673. Do you think the two are related?

I noticed the issue Priority is set to 'Minor', while I understand this is not a Critical issue for you, it's not minor for us. Atlassian provides a workflow that we adopted and use regularly that does not work, and it interrupts our workflow and causes us to have to spend extra time, that's not a 'minor issue' for us.