Any news on this? 

Well, the old editor in Confluence Cloud still has the functionality but it's not available in the new editor!.

Unfortunately, one cannot decide to use the old editor or the new or revert back to the old editor. This would be at least a workaround.

Bring this feature to the new editor and like the other users said this will fix the problems.

The "image library" mechanism described by Birgit Matuolis is exactly how we used the feature as well. It is a simple yet powerful use-case which was one of the major features which kept us using Confluence Server for so long.

If the PMs are interested in how the feature used to work, they can check directly in their own Server/Data Center Confluence documentation, which is still available online: https://confluence.atlassian.com/conf85/display-files-and-images-1283360011.html

It explains exactly what kind of functions the "Insert files" dialog was capable of, namely inserting existing attachments from the same page, searching for attachments on other pages/spaces and inserting them, inserting from the web via URL.

All we really want is to get these options back.

As to how we used it: We had multiple documentation spaces (for each major version of our product) and a central "image library" space where we would attach all documentation-related images. These could then be used in all the documentation spaces without having duplicates of the (mostly unchanged) images in each space. So, if an image did need to be changed, we would either upload a new version of it in the "image library" space and it would be change everywhere, or (if the old file had to be preserved), we would upload the changed file as a new attachment to that space and use it in new documentation spaces going forward, preserving the old image used in the older spaces as well.

Yes, the fact that the product manager put out a call for input on how the feature should work betrays the fact that Atlassian still considers this a feature request.

It is not a feature request. The feature we're asking for already existed and was removed. Yes, I understand that technically the cloud platform is likely it's own distinct product which never had the implementation that the on-prem product did, but that is beside the point. The point is you know exactly what we're asking for and you literally have the code to reference in order to know exactly how it should work and to recreate it however makes sense for your development workflow.

Hello all, I have developed a workaround for this for our team. However, it involves creating a Javascript bookmarklet and then using a source editor add-on to insert the resulting wiki code into the proper spot in the page. If you or your users aren't comfortable with that I wouldn't suggest deploying it. But if anyone is interested I can share the code here.

We have been using it for a few months and it is working. (Although we are trying to keep all of our existing pages in the Legacy Editor as much as possible due to these kinds of limitations.)

I agree with the other commenters on this issue. Restoring the attachment functionality that existed previously in Confluence Server would be a significant improvement for Confluence Cloud users. As 917f39338c5e mentioned earlier, the current limitations around attachments are frustrating - having to delete and reupload an attachment if its position needs to be changed, or needing to reattach the same document/screenshot on a different page. This unnecessarily hinders productivity.

It's interesting to note that Jira Cloud faced a similar issue in the past, and the ability to select existing issue attachments and insert them into a comment was later brought back. Implementing a comparable attachment functionality in Confluence Cloud could provide a similar boost in user experience and efficiency.

Overall, restoring the attachment capabilities that were previously available in the server version of Confluence would be a welcome change that aligns with Atlassian's goal of making their tools more productive for users.

Hi 5dd6d3cdd988 I don't think the user call is going to be helpful considering that Atlassian already has a working example of how the legacy editor works, as well as 3 decades of legacy product installs that can be used as examples. When Confluence moved to the cloud, we expected better, not worse. In some things, Confluence cloud gives us beter – built-in support for reusing multiple excerpts from a single page, for instance.

But on the other, core functionality went missing without any replacements that make it better. Attaching existing files (images, other content) that are already ON THE PAGE or at least IN THE SYSTEM. This is core functionality used by most every Confluence user to ensure consistency across multiple pages.

It's especially annoying when images are placed on the page and then need rearranging. 

Users understand that it's still in the attachment list. They just want to pick it again.

It's especially flummoxing for new-to-Confluence users. They just give up. 

Love that Suggestion Type and legacy-suggestion label....not really.
This isn't really a suggestion.  This is a seriously missing piece of functionality. 
We had a single source of truth, with versions!  That's completely gone and now we have trouble with people uploading and sharing out of date information, when previously we could manage it quite nicely.  This was a good way to get users to move over from some of your competitors.  Now we're back to making do with other tools, linking to them from Confluence, to make sure we're accurately sharing information.