Okay, this could possibly be a honest mistake. I, and 95% of users of the actual product, wanted to be able to link to external images, e.g. badges from build systems, etc. and have them SHOW as part of the confluence page. Fundamental functionally from the img tag, that has been in HTML from literally when images was implemented. Which is, IIRC, more than 30 years ago..

Atlassian has apparently read this requests as we want to be able to upload random images from around the world and attach them to the page. No wonder this has not been implemented in 5 years, as nobody wants this functionally. However, we are bloody screaming murder for not beeing able to LINK to images using URLs as has been standard for 30 years.

It seems to me, that the Atlassian employee Shannon S might be at some fault here, as she updated the description of the issue back in october 2019.

The workaround does nothing near what Shannon suggests. It just inserts a text link to the image. It does not SHOW the image.

I agree that the wording from the original poster could have been better, but it does not help that it seems nobody at Atlassian seems to understand how you use HTML? (How can this even be?)

5dd6d3cdd988 : We need to be able to link to and SHOW images outside our our Atlassian confluence instance. I need the new editor to support entering the url https://www.example.org/random.jpg and have this jpeg displayed using the image tag whenever the confluence page is shown or reloaded/whater. Not uploading it as an attachment, but just old-fashioned linking and SHOWING as the img tag was born to do!

How do we get you to support this functionality, that has been available in all system, inclusive Confluence, until you did not support it in the new editor from about 2018? Is there another issue on this, that we can watch and vote for?

Wow i just found the great hack mentioned below a few months back, it's worth repeating for anyone that missed it.

Paste this into plain text editor, then cut-n-paste it into the confluence editor.


When you save and then view the page it will load the image from the remote site just as the old editor did and as this ticket requests the new editor to do.  

Beats waiting for Atlassian to read the ticket description, reopen the ticket, and re-implement this feature in the 'new' editor.  C

It is really a miracle to me that it took you so long to do it completely wrong and so elobaratly complex at the same time.

Nobody asked for an "upload by URI".

Just use a normal link. Have you ever heard of <img src>? Do you know HTML at all?!?!?

I am really heavily disappointed.

5dd6d3cdd988  Not sure if I should assume the fetal position and cry under my desk or get myself checked in into an asylum because I'm stuck in a maniacal laughing fit...
THIS IS NOT WHAT WAS ASKED FOR!

It's almost like Atlassian are pathologically programmed to take something simple and mess it up for the enjoyment of seeing the howls of complaint from the user community... there's a phrase for that in psychological circles.. gaslighting !

It's wrong to close this issue. you didn't fix it, you changed the way you upload media - displaying images based on their links was never implemented or fixed

Just wanted to remind you that my extension can handle this issue for you

https://marketplace.atlassian.com/apps/1233867/remote-image

Thank you Atlassian for keeping me in business

28542cb4587a I would not hold my breath. The issue CONFCLOUD-1762 has taken more than 20 years to complete. They just don't get it.

I can't see the new UI, when is it actually getting rolled out to all tenants?

As someone else pointed out, the description of this feature `When adding media using links, we’ll try to upload them to avoid any unexpected changes for viewers of your pages` is entirely missing the point and is not what is being asked for.

We want to link a live image, usually a status badge ie for a last build status, static-analysis status, current live version status, etc - none of these work if you upload and cache the image - the whole point is to explicitly not cache this image but to load it live.

Please re-open this ticket - it is far from resolved

5dd6d3cdd988 this must be a joke: it took 5+ years to implement something that is not what your userbase is asking?

Unless I misunderstood, the post says "When adding media using links, we’ll try to upload them to avoid any unexpected changes for viewers of your pages" which means you are not showing the external image as is from its host (that is outputting a simple <img src="" /> HTML tag, but you are actually storing a copy of the "linked" image and use your stored version.

But this is not what everyone is requesting. 

How do you think that this implementation (that no one requested) can solve the use case of users that want to display the current image of a build status badge, or any other image that changes over time (and what we need is exactly to display the changed image over time)?

I'm not even surprised anymore of those bad jokes from Atlassian, after the huge custom-domain fiasco (https://jira.atlassian.com/browse/CLOUD-6999) which is even more self-explanatory of the way Atlassian doesn't listen to customers at all when designing the implementation of missing features in their cloud solutions.