• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Status Update 20 July 2023

      Hi everyone, the ability to add files inline in sentences is now live. We hope you enjoy the feature and it's useful for you!

      This ticket also speaks to two other features; the ability to add images inline in sentences, and the ability to reference files already added.

      The ability to add images inline is now in progress (you can watch this ticket for updates: https://jira.atlassian.com/browse/CONFCLOUD-68501).

      The ability to reference files already added is on the long term roadmap. Please vote on this ticket: https://jira.atlassian.com/browse/CONFCLOUD-65344 to help us understand if the feature should be prioritised sooner.

      All the best

      Owen

      Status Update 29 March 2023

      Hi everyone, sorry for the lack of updates on this ticket.

      Here's where we are up to:

      • We are actively working on the ability to be able to view an attachment inline vs having a thumbnail that takes up an entire line. This is mostly dev complete so I'll post when I have an update on rollout timings

      I note from the comments that the following issues are also needed:

      Furthermore we've also moved the ability for better image resizing (https://jira.atlassian.com/browse/CONFCLOUD-67554) into the research/design phase

      We know not having these features in Cloud has been problematic for many of you - so we've super excited to be working on these

      All the best

      Owen (PM on the Atlassian Media team)

       

      Status Update 15 December 2021

      Hi - I’m a Divya Sriram, a PM on the Confluence team. I recognize that it's been a while since you've heard from the team, so I'm here with the update we owe you.

      Solving the need for attachment links is high on our priority list. Currently, we are focused on critical work to improve table formatting and performance for Confluence Cloud pages - problems that also affect a very broad pool of users.

      Even though the solution to attachment links seems simple, there are a few technical considerations we need to tackle. We're actively investigating the best solutions to those problems and hope to start working on this in the next 6 - 9 months. We acknowledge that the delay on implementing this feature is frustrating for many of you. We will keep you updated on our progress.

      If you want to chat live, please grab time with me here: Divya Calendly Link

      Status Update 3 December 2020

      Hi all!
       
      My name’s Jonno and I’m a PM on the Atlassian Editor in cloud. This is an update on the status of this ticket/request.
       
      This ticket alludes to a number of different features:

      1. Being able to view an attachment inline vs having a thumbnail that takes up an entire line.
      2. Being able to link to an attachment that exists elsewhere in Confluence.

      We have a roadmap item in Q3 (Jan - March) to start work on the first problem - being able to view an attachment inline vs having a thumbnail that takes up an entire line. To be clear - this item will also include the missing ability to insert an already present image within the attachments of the specific page.

      We do not yet have roadmap work assigned to the second problem - being able to link to an attachment that exists elsewhere in Confluence. We are, however, exploring what we could do in this area. 

      I’ll continue to update this ticket as I have more to share.
       
      If you ever want to have a chat in person about the new editing experience, my calendar is always open to book in a 1:1 Zoom call - https://calendly.com/jkatahanas/editor.
       
      Please keep the feedback coming 🙂 
       
      Cheers,
       
      Jonno | PM for the Atlassian Editor (Cloud)

      Problem Definition

      With the latest editing improvements, the ability to display an attachment file as a link has been removed from the Link Macro. It is now only possible to link to known pages with this macro. 

      Displaying a link to an attachment in a page is only possible by attaching it using a macro directly or as a preview.

      Suggested Solution

      Provide ability to link text to attachments using the Link macro. 

      Workaround

      By using the Attachments macro, you can obtain the URL of an attachment and link text to that by pasting the link into the Link Macro.

      Workaround 2

      By visiting the `Attachments` page through the `•••` menu, you can right-click on the attachment links and `copy link address`. Then use that as a text/blue link.

            [CONFCLOUD-65302] Ability to link text to an attachment in editor

            Hi everyone, the ability to add files inline in sentences is now live. We hope you enjoy the feature and it's useful for you!

            This ticket also speaks to two other features; the ability to add images inline in sentences, and the ability to reference files already added.

            The ability to add images inline is now in progress (you can watch this ticket for updates: https://jira.atlassian.com/browse/CONFCLOUD-68501).

            The ability to reference files already added is on the long term roadmap. Please vote on this ticket: https://jira.atlassian.com/browse/CONFCLOUD-65344 to help us understand if the feature should be prioritised sooner.

            All the best

            Owen Wallis added a comment - Hi everyone, the ability to add files inline in sentences is now live. We hope you enjoy the feature and it's useful for you! This ticket also speaks to two other features; the ability to add images inline in sentences, and the ability to reference files already added. The ability to add images inline is now in progress (you can watch this ticket for updates: https://jira.atlassian.com/browse/CONFCLOUD-68501 ). The ability to reference files already added is on the long term roadmap. Please vote on this ticket: https://jira.atlassian.com/browse/CONFCLOUD-65344 to help us understand if the feature should be prioritised sooner. All the best

            Ian Kaplan added a comment - - edited

            I submitted some of the early comments on this feature years ago. After years Atlassian has been unable to make the new cloud editor as good as the old "legacy" editor. This is shocking.

            I sent complaints to the co-CEOs and everyone else I could think of. They basically don't care. I speculate that the CEOs are so rich that they don't care anymore. They're enjoying their money and they don't really care about running the company. 

            The fire Jira video was great. Unfortunately, firing Confluence is not as easy. The support from Atlassian is shockingly bad and the new editor is dramatically worse than the old editor. Perhaps all of this is due to the fact that there are no real alternatives to Confluence, at least that I have found. 

            I have tried Notion and it is not as good as Confluence.  Also, I have over a decade of material on Confluence.  This includes engineering notes, but also information about my company, taxes and so on.  There is no practical way to get all this data off Confluence. Even if I could, I would worry that the company that supported the produce would go out of business. As bad as Atlassian is, I don't think that they're going to go anywhere.

            Sadly, all this adds up to terrible support, since Atlassian seems to realize that they have a captive audience.  Where are you going to go?

            Ian Kaplan added a comment - - edited I submitted some of the early comments on this feature years ago. After years Atlassian has been unable to make the new cloud editor as good as the old "legacy" editor. This is shocking. I sent complaints to the co-CEOs and everyone else I could think of. They basically don't care. I speculate that the CEOs are so rich that they don't care anymore. They're enjoying their money and they don't really care about running the company.  The fire Jira video was great. Unfortunately, firing Confluence is not as easy. The support from Atlassian is shockingly bad and the new editor is dramatically worse than the old editor. Perhaps all of this is due to the fact that there are no real alternatives to Confluence, at least that I have found.  I have tried Notion and it is not as good as Confluence.  Also, I have over a decade of material on Confluence.  This includes engineering notes, but also information about my company, taxes and so on.  There is no practical way to get all this data off Confluence. Even if I could, I would worry that the company that supported the produce would go out of business. As bad as Atlassian is, I don't think that they're going to go anywhere. Sadly, all this adds up to terrible support, since Atlassian seems to realize that they have a captive audience.  Where are you going to go?

            TJPII added a comment -

            @ChrisRehberg and others are spot on about how ridiculous Atlassian responses have been.  Many features in the old editor that worked fine, enhanced productivity, and were in daily use were removed in the name of improving the user experience.  That goal was and remains today, an abject failure.  While some items in the editor were improved, the overall user experience was not, and users have been expressly vocal about it.  But over a years-long timeframe, Atlassian has repeatedly shown little interest in taking meaningful action on those concerns, no matter how vocal or valid.  The lack of response is so bad, users have resorted to tying to publicly embarrass Atlassian just to get some attention.  But even that has little effect beyond a joking acknowledgement.  It makes me believe Atlassian's response is willful.   Even if this one item finally gets addressed after being open since 2019, I won’t quickly buy into the idea that "Atlassian Cares".  

            TJPII added a comment - @ChrisRehberg and others are spot on about how ridiculous Atlassian responses have been.  Many features in the old editor that worked fine, enhanced productivity, and were in daily use were removed in the name of improving the user experience.  That goal was and remains today, an abject failure.  While some items in the editor were improved, the overall user experience was not, and users have been expressly vocal about it.  But over a years-long timeframe, Atlassian has repeatedly shown little interest in taking meaningful action on those concerns, no matter how vocal or valid.  The lack of response is so bad, users have resorted to tying to publicly embarrass Atlassian just to get some attention.  But even that has little effect beyond a joking acknowledgement.  It makes me believe Atlassian's response is willful.   Even if this one item finally gets addressed after being open since 2019, I won’t quickly buy into the idea that "Atlassian Cares".  

            Hi Iain,

            Yeah - that's a cool video and so on point.

            I agree - there is nothing that was as powerful as the old Confluence. I too used it for ages (even since the version before the prior version) and recommended it highly. I tried voicing to Atlassian that they should split the new and old products as different offerings for different users but like you say, you can't get heard unless you pay a premium - and truth be told, I don't think paying a premium will get you heard anyway.

            Man, if Elon can fork out to buy Twitter, imagine how cheaply he could hire just a single dev team to take the 80:20 rule to Confluence - grab the 20% of features that are most powerful and most used and that accomplish 80% of what we need and kick it off as a new product offering. I would love to head and oversee the design of such a product, but I sure don't have the budget to put my money where my mouth is on that one.

            Chris Rehberg added a comment - Hi Iain, Yeah - that's a cool video and so on point. I agree - there is nothing that was as powerful as the old Confluence. I too used it for ages (even since the version before the prior version) and recommended it highly. I tried voicing to Atlassian that they should split the new and old products as different offerings for different users but like you say, you can't get heard unless you pay a premium - and truth be told, I don't think paying a premium will get you heard anyway. Man, if Elon can fork out to buy Twitter, imagine how cheaply he could hire just a single dev team to take the 80:20 rule to Confluence - grab the 20% of features that are most powerful and most used and that accomplish 80% of what we need and kick it off as a new product offering. I would love to head and oversee the design of such a product, but I sure don't have the budget to put my money where my mouth is on that one.

            Iain Whyte added a comment -

            Chris R,

            I hear you. I've been a huge fan of Atlassian over the years, I think I first started using Confluence at version 3, in like 2010 or something. Last little while, it's getting really really hard not to start to hate on all of it. The force move to cloud, the rediculous editor that is missing just basic features that you MUST use for new pages (but the old editor is still there, for old pages!?!?), the fact that you have to pay by credit card to go non-punitive terms. I think I might be close to done.

            This nails it. https://www.youtube.com/watch?v=LPCUAgzUt2k I just wish there was a Confluence equivalent.  

             

            Iain Whyte added a comment - Chris R, I hear you. I've been a huge fan of Atlassian over the years, I think I first started using Confluence at version 3, in like 2010 or something. Last little while, it's getting really really hard not to start to hate on all of it. The force move to cloud, the rediculous editor that is missing just basic features that you MUST use for new pages (but the old editor is still there, for old pages!?!?), the fact that you have to pay by credit card to go non-punitive terms. I think I might be close to done. This nails it. https://www.youtube.com/watch?v=LPCUAgzUt2k  I just wish there was a Confluence equivalent.    

            @owen wallis - can you hear yourself?

            This ticket title is "Ability to link text to an attachment in editor". It was raised in 2018.

            Now your latest update says "Ok, you asked about that basic HTML function of using text to link to a downloadable file - you know - that entered the HTML language back in the 1990s - but here's what we're going to do: first... we'll DISPLAY ATTACHMENTS INLINE!! Woohoo! Phew. But that's a lot of hard work. That's going to take us FIVE YEARS. You know, after that, here's what we'll do ... we'll DISPLAY IMAGES INLINE .... OMFG!!!! How radical is that!Unable to render embedded object: File (?? If our track record is anything to go by, we won't listen to your feedback and we won't provide any updates for at LEAST another five years to get that one done. Oh, AFTER that we will look into the possibility of 'referencing files' that have already been attached to the page. I don't know why we worded it that way. In fact, I don't even know for sure if that's actually a match for the title of the ticket and what you asked for, but whatever it is, I'm sure the whole dev team will be a bunch of different people by then and they won't know or care either, so we'll just do something and tick the box that says 'done'. Oh yeah, while we're promising stuff, let's give you the ability to RESIZE IMAGES - NO WAY) not found.!!! That is AWESOME!!!! What's that? Huh? Oh yeah - you are right ... all of these features worked in the editor that we just dropped without notice in order to give you this Kindy Konfluence five years ago. (blush)"

            It takes a lot for me to vent sarcastically, but Atlassian, for crying out loud, your "service" is appalling.

            Chris Rehberg added a comment - @owen wallis - can you hear yourself? This ticket title is "Ability to link text to an attachment in editor". It was raised in 2018. Now your latest update says "Ok, you asked about that basic HTML function of using text to link to a downloadable file - you know - that entered the HTML language back in the 1990s - but here's what we're going to do: first... we'll DISPLAY ATTACHMENTS INLINE!! Woohoo! Phew. But that's a lot of hard work. That's going to take us FIVE YEARS. You know, after that, here's what we'll do ... we'll DISPLAY IMAGES INLINE .... OMFG!!!! How radical is that! Unable to render embedded object: File (?? If our track record is anything to go by, we won't listen to your feedback and we won't provide any updates for at LEAST another five years to get that one done. Oh, AFTER that we will look into the possibility of 'referencing files' that have already been attached to the page. I don't know why we worded it that way. In fact, I don't even know for sure if that's actually a match for the title of the ticket and what you asked for, but whatever it is, I'm sure the whole dev team will be a bunch of different people by then and they won't know or care either, so we'll just do something and tick the box that says 'done'. Oh yeah, while we're promising stuff, let's give you the ability to RESIZE IMAGES - NO WAY) not found. !!! That is AWESOME!!!! What's that? Huh? Oh yeah - you are right ... all of these features worked in the editor that we just dropped without notice in order to give you this Kindy Konfluence five years ago. (blush)" It takes a lot for me to vent sarcastically, but Atlassian, for crying out loud, your "service" is appalling.

            Hi f7202484c9d6 (and other folks watching), 

            Pending no major bugs being found during rollout, the ability to be able to view an attachment inline will be going live in July

            While I love a good t-shirt design, hopefully we won't be needing one for this ticket

            Owen Wallis added a comment - Hi f7202484c9d6 (and other folks watching),  Pending no major bugs being found during rollout, the ability to be able to  view an attachment inline  will be going live in July While I love a good t-shirt design, hopefully we won't be needing one for this ticket

            Uhhm - it is now the 7th of June...years have past and also 3 months have past since the latest update. 

            The least Atlassian could do is explain why t.h. this is such a difficult issue to solve??

            Please update!!

            Or is this another "CLOUD-6999" issue we'll be making t-shirts of in the coming years?

            Han Limburg added a comment - Uhhm - it is now the 7th of June...years have past and also 3 months have past since the latest update.  The least Atlassian could do is explain why t.h. this is such a difficult issue to solve?? Please update!! Or is this another " CLOUD-6999 " issue we'll be making t-shirts of in the coming years?

            Great news Owen, thanks for the update. Can you please give us an estimated date on which this feature will be available again? As you can see, it has been an open issue for years already.

            Michal Katz added a comment - Great news Owen, thanks for the update. Can you please give us an estimated date on which this feature will be available again? As you can see, it has been an open issue for years already.

            David Grogan added a comment - - edited

            Great news that this is finally in the works. Any update on when we can test it?

            David Grogan added a comment - - edited Great news that this is finally in the works. Any update on when we can test it?

              owallis@atlassian.com Owen Wallis
              smackie@atlassian.com Shannon S
              Votes:
              819 Vote for this issue
              Watchers:
              469 Start watching this issue

                Created:
                Updated:
                Resolved: