They don't realize they have killed the engine and they keep bragging about the paintwork and fine leather seats... who cares if we can't run the damn thing.

Keep sending us your email propaganda Atlassian about how great the cloud is, because it's not working. While you seem to be gathering interest forever, us, the users start looking elsewhere.

We are NOT moving to cloud with all these issues and deprecated functionality.

@Jack, I would be very interested to get in touch with you to learn what alternatives you propose to your customers.

I have to often remind people to NOT use the new editor but to select the legacy editor template when creating documentation. Our style uses specific pixel sizes and borders on images. (Otherwise, the images look floaty and unprofessional.) Also, our images are indented two spaces, which I can't do on the Fabric editor. It's not usable for us as is. 

370 votes and 130+ very frustrated comments. O Great Confluence Cloud Team, hear our plea, we beg of you.

They have had a great server product and now they deliver only this piece of... too sad 

I can't believe that this Job is closed. 

Using page property reports with images is a desaster... complete not usable, absolute scrap

In our case, we will surely not move to cloud until the critical features that we currently have on prem (including resizing a images by pixel and support for multilingual pages (currently using the Scroll Translations extension)...) are made available on cloud...

Why are you continually REMOVING CRITICAL FEATURES?!?  It baffles the mind.  If I can't resize an image, I have no control over it, and it's useless in my document.  And now I can't even place it where I want, like in the middle of a sentence.  If we never had this feature in the first place, that would be one thing (and wouldn't be good), but to have the feature available and have us using it happily for (years?) and then TAKE IT AWAY makes me really pissed off.

This isn't the only important, basic feature you've removed.  This is just one of many.  STOP.   DOING.   THIS.  And prioritize restoring features!!

Argh.

Will there be an update sometimes in the near future? The functionality to set an image to a certain pixel number or at least 3 different fixed sizes is missing. This is a major feature for us. 
With only the resizable bars on the side it is impossible to get 20 pictures to the same size. 

jwilson14 The Cloud version had the feature to control the size of the image. They just decided to drop it way. 

When I have been looking the new features of the Confluence and Jira  I have feeling that the people develop the service does not have any idea how customers use the features. 

Having the ability to control the size of an image is super critical to producing a professional document. You have this in a proven application Confluence Server. Why is this fundamental editing feature no in Cloud?

I agree this is a bug an not an improvement suggestion - for crying out loud.

We are a little company using Confluence Server and (everybody knows why) looking to move to Cloud.

It is jaw dropping to discover the level of inconsistency between the Server and Cloud editor. 

We use many pages where we shrink images to 30px "avatar size" to show up in page property reports. You have no idea what you're doing to your customers by breaking this functionality.

I've been working with Confluence for over 10 years, and now I finally snapped (apologies) - I 'm not in love anymore - you are killing the experience.

On top of that, you make it a trademark for issues to remain open forever... or close them as FIXED while the resolution is: "it is how it is - live with it, or..."

We are not amused Atlassian.

Please elaborate why this ticket is open for over a year?

315 votes and still gathering interest. This should be a bug, not a feature request. The sizing handles are unreliable and buggy and they almost never achieve a precise result. Sometimes images get blurred for no particular reason, or shrink to a ridiculous size, or just don't look right after publishing. The whole thing is broken.

I still don't really understand the logic of stripping out features and redesigning it this way – Pixel and percentage sizing was just fine the way it was before. Other software/apps that have drag-to-resize functionality (Google Docs, Word, Photoshop, Wordpress, MS Paint...) all have the option to type in precise sizes. Literally all of them. There was no discernable reason to remove such a basic ability.

We have got still the same problem - to use images in the new editor is very impractical. I can't see any advantage to the image size adjustment in the new editor.

It takes to much time without good result 

@Ariane R. we have the same issue. Sometimes it helps to resize the image too much before publishing and the page view is almost okay afterwards. But this doesn't work everytime. Sometimes we deleted an image and added it again to have it in the wished size. But also here: it doesn't work everytime.

My team is running into an issue: when we try to resize images inside of a table using the handles in the new editor. It resizes the image while in the editor view but does not resize once Published or when viewing the page through a linked add-on. Being able to specify the size of an image precisely is very important to maintain consistent content across our Knowledge Base and hopefully eliminate the issues with using the handle resizer within tables. 

Our client-facing documentation uses a lot of images. For style and quality we want consistent sizes, spacing, etc. Every time I create a page, I have to copy an existing legacy editor page so that I have all the functionality that I need to produce a quality product that enhances our client's perception of our company. It would be near impossible to have to use Gliphy or any other tool to address images. 
Copying an existing page is the best workaround for us. 

The old "legacy" editor was made for B2B use and it did the job what our team needed in our work. The new editor misses the essential old feature like image resizing and presentation of the images in various sizes. Also it is not possible to any more include pictures that are already attached to the page. I am using Gliffy nowadays to resize the images, that means I need to do quite many extra steps to get the result I want.

I don't know for whom you have designed the new editor. In my opinion it does not have good fit for B2B work as it has introduced hyphens and Gliphy images, which are totally useless in worklife where the aim is do good documentation that can be shared in your own organization and externally.

Not sure where to post this comment, but this was the most similar case I could find...

Let's say I add an image to a confluence article and publish it. When I am in confluence reading this article I can click the image and enlarge it. As a customer using Jira Service Desk reading this same article, the customer is NOT able to enlarge images. It is very messy if all the images must be full size on the confluence page in order for customers to see these.

Also, if I add a Power Point presentation in order to avoid the issue of having too many large pictures in a row showing on the page at the same time, the customer only sees the first slide in Jira Service Desk when viewing this documentation, and has no way of enlarging this PPT and no way of viewing any of the other slides. What am I doing wrong here? What am I missing? It would be a shame if this type of functionality is only for Confluence users but not for Jira Service Desk customers viewing the same exact documentation. 

Well I am glad you found it using /expand but we can also see it in navigation as well. I myself always use the / command to insert macros so I had to go check and see if its on navigation and sure enough it is. 

Correction: it looks like you can't navigate to it, but "/expand" does insert the macro!   Thanks Arthur! 

We can't see it either. 

The new editor requires too many workarounds, so I still use the legacy editor by copying an existing page, deleting the content and then putting in my new content. I can resize pics, add borders, comments and all the good stuff that is needed for our client documentation. 

The new editor doesn't fit our needs. 

It is for us, we use it all the time, its just  /expand. Works great.

The expand macro may be in the new editor but it is still not accessible.

The expand macro is still there in the new editor.

Thank you for the emoticon hack, I will try it!   There are (many) days I really miss the old editor.

On that note, is there a workaround for the old "expand" macro? I miss that one too... and the "panel" macro.. but I digress. 

Well aware of all the issues but its better than a big blob on your page.

Atlassian recommends the custom emoticons as a replacement for inline images, however... there are known issues, including custom emojis not being  visible for anonymous users, not being visible when used in some macros, not being visible in exported PDFs and more... so be careful!  And please add your feedback this issue: Allow Images to be inserted inline or in an sentence in the New Editor https://jira.atlassian.com/browse/CONFCLOUD-68501

Using Emoticons here as well but its only in desperation!!!!

Hi @Doug Robinson,

I managed to get around this issue for particularly small images that you want to display in-line with text by using the built-in Custom Emoticon functionality.

It's a bit of a hack, but is much more appropriate for icons you want to appear in your sentences than the image feature.

Jack

Maybe this is the wrong ticket, but I don't need to size by pixel, the handle is good enough, but the minimum size is HUGE. I don't want an icon to take up half the page, I just need it large enough to recognize and click (where it's linked to other pages). 

Please implement this basic function. Thanks 

Really surprised a feature that was there is not available anymore. It's incredibly frustrating to be editing and resizing images before uploading them to confluence.

We are quite suffering with the new editor, we would need this feature to be back, it's a basic function in any editor to size and place an image a precise way. It's quite disturbing with a mature product like confluence which is on the market since a while to have the feeling going backwards. Thanks for your understanding!

you gotta be kidding. why would you remove such feature?

Seems like its gathering dust and not interest. I am not one to b..tch but this has gone on long enough not being able to size images by the pixel. I would have thought Atlassian has had all the feedback they need on this!

The new editor is such an exercise in frustration. I can no longer align images arbitrarily, nor size them appropriately. I really do regret moving off of our older on-prem instance. The old editor may have had quirks, but in the new editor anything that has to do with sizing and aligning images is just not well thought out. 

Yes cant stress enough that the image resize feature is very important.

Please bring this feature back.   

I definitely need this feature. I have rejected new documentation platforms because of this. Please bring it back.

I want this feature back!

Sizing by grid is not functional for me.

https://getsupport.atlassian.com/browse/JST-586912#

Agree - this is needed

What is going on with this issue? So many votes. I can't change the size of the picture.

Just have to add that while adding information to this ticket on the Legacy Editor still being accessible may help some people, it does not provide a solution for those of us who want to use the new editor. It comes back to feeling unheard as a company who has no interest in using your software in a front-facing streamlined way on mobile. We simply use it differently, and standardizing sizes with your (unfortunately  unreliable) grid system has created a lot of pain for my teams. I get complaints about this several times a week, and it impacts work times. 

While I know designing something like this is extremely complicated and there is no pleasing everyone, I really feel like control over this should not have been something removed from core document design infrastructure. 

This change, and that it's been out there for months is ridiculous.
Who in their right mind would want to remove a Pixel resizing preference 0- and replace it with "click and drag"?
Come on, pull the other one.
Someone forgot to copy and paste a line of code if you ask me.

Never understand why release new things and remove old things at the same time. New things should be additions or optimizations, but never removal of old good features that everyone is happy about and are using for ages. Adding of Images in new look is now a terrible experience  

I very much want and need the image sizing capabilities that were available in the old Confluence editor.  Overall... while we have gained some nice new features, we lost some AWESOME old features... we lost A LOT of awesome old features.  Please bring this one back!

To have not reall an influence on the size of an image is apart from the source-page quit horrible if the image is used in a detailsuumary.

On one side the image is so small that you have no chance to identfy the image, on the other side, the image is so large, that it si impossible to create an overview.

There was the old procedere multiple better.
Please add a conscious control of the image size again

It's very difficult to resize an image. Please add this feature to the new editor.

Please restore the functionality to resize pictures by pixels. This was a fast and easy way to create well looking documentations. The new editor resizing behaviour is just annoying.

I agree, not being able to control precisely the image size anymore (including png, svg...) is very frustrating ! It is a bit difficult to understand why a new editor lacking many basic features was released to the general public 

This new grid-based image resizing is ruining my pages. Removing the ability to keep my images in their original size?? TERRIBLE.

This should be high-priority. This is a basic, core wiki need.

Very upsetting. Please address promptly. 

The image editing option was available in the old version and vanished after the update.
Extremely upsetting!! 

@d0ece3ceb40a 

I hope it is fixed as well. We have two Confluence accounts. The older one is still able to create pages with the legacy editor but the newer one only has the ability to use the new editor now. 

I have had to use the "copy method" on every new page for a couple months now. =( 

I create every new page using "COPY" from exsiting page with legacy editor. Is it going to be fixed ?

I think I am in the twilight zone. I was editing an image yesterday and low and behold I could change the pixel size in the fabric editor. Wow I thought this has finally happened but alas I must have been dreaming as its gone again today.

172 votes. 75+ comments.
Where is the moderator's comments/feedback?

Starting to think our feedback drifts into the ether.

ATLASSIAN where are you?

I think they are losing credibility with doc professionals and everyone is going to evaluate if Confluence is the right tool for them. You cannot upend a good product and expect no backlash.

I hate to say it, but I agree with The Guv - I have no idea what possessed Atlassian leadership to take a good product and attempt to dumb it down to an extent that everything that made it fit for purpose was removed.  This may be looked back at, in years to come, as a classic corporate error.

Another classic example of the new editor being released without many features which I considered as Must Haves. TBH it makes me look at alternative products

The new editor is completely unusable without this feature. And the now available "bars" right and left of the images just don't work, especially in the new tables (which are also, sorry: mainly unusable. Only to make editing responsive...)

We are a publishing house for school books and therefore have a lot of images - as well as screenshots for explaining tools and so on, this is essential for us. Hope there will be an improvement soon.

In our documentation we use a lot of screenshots. These are not always printed page width and to make sure that all images are printed the same in the exported PDF file, we used to just set the pixel width all to the same size. Really would like this option back!!

Shawn - I use this "contact support" link. It opens a help ticket and they're very good a getting back to you, even if it's just a question or you need help. https://support.atlassian.com/contact/#/

I usually give the community a chance to answer first!

I agree with Wendy (BTW, thank you). My vote should also count for more; about 220 votes!

The new editor is probably quite new for new users who are not aware of the many feature regressions, but it's a train wreak for all long-term Confluence power editors, with a large investment in existing content, and style standards that are about to get disrupted. 

It's made worse by Atlassian not properly communicating with us. I mean, when are they going to fully deprecate the old editor? (the correct answer is not until the new editor is fully non-regressive)... no one seems to know when this is happening. In the editor, the old editor "Blank Page" button used to include a warning that it was going away soon, but now there is no warning; is Atlassian listening to us? My own questions to Atlassian have not been answered, either PM or in the forum.  

Wendy, if you could add 500 votes to this issue that might actually help move the needle.

Well said, Shawn! It's so aggravating that we have to wait for basic features that used to work perfectly fine to be fixed. Atlassian support only suggests voting on the issue to raise its priority. These basic fixes should be _Atlassian's _high priority. I am the Confluence Admin for a big company, and colleagues ask me to contact support about issues. I cannot ask my colleagues to waste time voting on issues. As their representative, my vote should count as 500!

Taking away image resizing by pixel is one of the most bewildering decisions that Atlassian has ever made! Not only was this option inexplicably removed, the strange and undesired automatic sizing of images makes editing with images almost unusable. 

I am only aware of one editor in the wiki or full document categories that can't do pixel size adjustments and that's Google Docs, but at least I can download a free add-on (wxh). 

It's almost as if Atlassian is completely out-of-touch with what their users need. 

k.mchardie, please consider voicing your frustrations here: https://community.atlassian.com/t5/Confluence-Cloud-articles/What-s-New-in-Confluence-Cloud-January-2020-Edition/ba-p/1265275

In the so-called Community, you can also @mention Confluence Cloud product managers including @shrey and @avinoam. Sadly, they are unlikely to respond because it is unusual for Atlassian employees to acknowledge challenges with the product.

I'm here looking for help on Confluence Cloud - it seems it's all the fault of the New Editor?  I've used Confluence for years - this new editor is just going backwards.  I cannot design user-help pages (that we are building on cloud) the way I want them in this new editor - and the entire experience is frustrating and annoying.  I can't believe Atlassian made this backwards move - I suppose with all the UX experts, Testers and Developers thay have - they have got to give them tasks to do. 

Why reinvent the wheel, if the wheel worked just right the way it was?

Baffled that Atlassian would remove this basic functionality. Why? Editor functionality is becoming less usable with every release.

I agree with everything above. This was a feature of the old editor that is not supported by the new one. 

I've linked my question on the community with example screenshots:

https://community.atlassian.com/t5/Confluence-questions/Image-scale-in-new-editor/qaq-p/1266846

Hopefuly the old editor is still available when editing old pages.

My workaround ? never more create a new page, but copy an old page to start working

Sad but true...

How long will we have to wait before having an answer and a fix ???

For the record, I am free to call a spade a spade here in Jira because I am using my years-old Atlassian account required for day-to-day administration of Jira and Confluence. If I were to make the same comments in the so-called Community, my account would be swiftly and irrevocably blocked. Been there; got the T-shirt. Not impressed. 

It is easier for Atlassian to say nothing than attempt to defend the indefensible. No one in their right mind would sanction the user-hostile decisions that have been made to introduce a replacement product that offers only a subset of the features of its predecessor. Sadly, complaints from every quarter are little more than noise to be filtered out.

Caitlin Main – Completely agree. I'm shocked that there's no official response from Atlassian regarding what data they relied on to arrive at this presumption. Further, little do they realize that features need to be backward compatible. This is breaking change for possibly thousands of users. Many of whom will only realize when things go for a toss. Talk about throwing the baby with the water!

"The rationale for this change, among others, was that pixel level control was overwhelming for most users making it hard to create beautiful and readable content easily across any screen."

I'm quite curious as to what the actual data on this response is. I feel like there had to be a better way to offer predefined image sizes to users who were "overwhelmed" by the (very simple?) old system that didn't involve gutting basic functionality that is integral to companies who use Confluence for custom standardized design documentation? My development teams are very disappointed and frustrated by this change. 

Kelvin Hill - Our company does the same, using Confluence for both internal documents and also as branded documentation on features and use for our clients. In order to demonstrate features, we use a lot of application screenshots, too. This loss is greatly affecting our ability to serve our customers. 

Tan Rong Wei, you were spot on when you wrote "provided you only have texts in the articles."

Sadly, we don't need a simple text editor. In addition to many company-internal text documents we collaborate on, we also use Confluence to prepare and export branded documentation for our clients. We have been working around the legacy editor's limitations and quirks for many years because it is sufficiently flexible to allow us to do so.

The new editor removes much of the functionality and also strips out the flexibility. In respect of this specific issue, we have consistently failed to display our images (many of which are application screenshots, which must be displayed at a specific resolution rather than a general size of x-small, small, medium, large, etc.) in the new editor in a consistently satisfactory way. It is immensely frustrating and causes us say no end of rude words about the decision makers at Atlassian.

While our frustrations have been acknowledged, I have yet to see much evidence of any action beyond empty acknowledgement.

It increasingly does look like they are abandoning the old editor simply because it is too buggy. To their credit, the new editor is a lot less buggy, and streamlined to use, provided you only have texts in the articles. 

Taking away the ability to re-size by pixel is a totally unacceptable loss of functionality. Anyone else going to the Summit? Maybe we can get an actual answer there? This is functionality we desperately need back.  

@Kelvin Hill The exact issue of what we are afraid of. We have already discussed if/when the old editor is taken away and the new editor no longer meets out criteria, the answer is not to adapt to the new editor, it will be to find a product that does what we want it to do. 

Currently the new editor is not an option for us with the image sizing options (or lack there of) available. Without being able to specify how large we want the image, the images are usually too large. 

Not something we will be working around. A complete blocker for our docs. 

Similar with table sizing/positioning and multiple other issues. 

Edit:

Also, the solution to purchase plug-ins to fix problems that weren't problems will not be acceptable. 

@Roz Turner. I only learned about the Fabric Editor in October/November 2019, but I understand it was made available to some folks almost a year ago. At the risk of angering the Atlassian gods, I suspect the fact that this issue has persisted for almost a year without anyone showing any interest in resolving it or even admitting that it is unacceptable doesn't bode well. I imagine it has been decided that we must learn to live with it or find an alternative product. They don't want to come out and say that directly, of course, so they simply maintain this ticket as "Gathering Interest" without assigning it to anyone. The Confluence user base is sufficiently large to warrant such complacency.

I'd like to add my voice to this as well as my vote. Of all the irritating changes made to the new editor, this is by far the worst. Our company uses Confluence extensively and the inability to resize images now means we have comedy-sized, stupidly large screenshots in our documentation which we can do nothing about.

Removing this option is a massive hindrance; instead of simplifying the editor, you're limiting users' options by removing something that already worked. Users should be given the choice as to whether they want to resize by grid, or by pixels. I'm fairly certain that removing key features is the least efficient way to retain customers. Please fix this.

@Julia Wester. Sadly, you've misunderstood the roadmap. I have included a screenshot below, but I suspect it won't attach correctly, so I will also explain in text.

Here are the roadmap column headings and the values for the Image sizing entry:

Feature: Image sizing
Legacy editor:  [green check mark] pixels
New editor: [green check mark] grid
Will it be available in the new editor: Available
Track the backlog: CONFCLOUD-67554 - Resize image by pixel on new editor - GATHERING INTEREST

If you simply view the Image sizing entry in the table without checking the column headings, it looks like pixels and grid sizing are supported in the new editor. Currenly, only grid-based image sizing is available in the new editor, and it produces terrible results if you attempt to align an image in any way other than the default or resize it. I remain shocked that the many glaring bugs with images remain unresolved.

If we are really lucky, image sizing by pixel will be added to the new editor at some point.

I am so confused about how resizing is marked as available: https://confluence.atlassian.com/confcloud/confluence-cloud-editor-roadmap-967314556.html?_ga=2.79383252.1187993251.1579073416-313053509.1570455679 I just added an image to a page (not in a table) and can't find the option at all - not to mention it added hundreds of pixels of padding above and below my image and pushed content so people have to scroll. Just WHERE do I find this ability to resize images?

No more  possible to design pages including small pictures or icons.

Working myself in software industry, I can't believe introducing a so big regression in a product...

Please fix it ASAP !

The option to edit image settings (resize, paragraph position) with the new tool is not accessible for images in a table.

They need to be resized/positioned outside of the table, then moved.

This feels like a bug, and is a frustrating experience.

I doubt how many users are aware of this, Kyle. Obviously, Atlassian has not done any outreach to see if people care or not. Their policy seems to be shoot first and ask questions later. 

I think only 62 votes is not a lot. Doubt it's enough to force change/catch their eye.

Those who have taken the time to comment on this thread should get everyone they work with who is impacted by this problem to vote for the issue.

Can Atlassian bother to explain what the issue was with the old image resizing? We have a huge doc portal with custom image sizes. How do the wonderful folks at Atlassian expect me to handle this change? We either need to have differing image sizes for old and new docs or refactor the old images to suit the new editing experience. Is this a software company that thinks about backward compatibility or not? Please do not force your new editing experience on us without resolving the many kinks in the new editor!

The status of this ticket amazes me – "Gathering Interest" – really? You break existing docs and then find out how many users are impacted?

This doesn't even make sense. I copied four images that are exactly the same size (80 pixels) on an old page in Confluence and tried copying them over into a page in the new editor, into a table.

The images re-size on their own when I paste them into the new page. I have no ability to drag to change the size to get them BACK to being all the same size. My only two options are to either deal with the inconsistent icon sizes, or delete the icons. 

Sizing images is the new editor is terrible; they snap to some arbitrary grid, and you can't shrink them below some unreasonably large size. I want the legacy image mgmt back!

Thanks, Kim. Your proposal has already been suggested by a number of frustrated users (including me) in a variety of threads. The problem we face, however, is that Atlassian has pledged to withdraw the old editor entirely at some point.

Personally, I wouldn't want to be in Atlassian's shoes right now. I, for one, have documentation I generate in Confluence that I deliver to paying customers. That content simply isn't supported by the new editor, so I cannot and will not migrate it. Does Atlassian expect me to delete the very content I have been creating in the tool we have been paying them to use for years? There is 0% chance I'm going to roll over without a fight.

Ladies and Gents

I have discovered that the original content has not been affected by these changes - its only when you create new content.  So that means I can resize my original work, no problem!

However, I also discovered that you can copy content and the old style resizing is available.  Simple interim resolution  -  take an original page, copy it, delete the original content and then you are free to add images and resize as before.

It works for me!

Kim

Hi.

I'm Angelina form Wafer stick manufacture in Indonesia.

I want to ask you related Confluence could features. Could we ask you email?  Or Could we invite you to do conference call with us to show how the confluence cloud working.

You can contact me by email a.qaspvsys2@seasonalsupplies.co.id

Thank you,

Regards,

Angelina

Communications with local Atlassian support personnel in my region yielded the following comments (theirs, not mine).

"However, we might be able to enable flags for particular elements/macros that your business requires it, this will be handled on a case-by-case basis and the flags availability. Please do let me know if you have any further feedback or concerns that I can share with the Product management team."

So I guess we'll just have to keep bugging their support with requests of features that are important to us. The local support personnel did promise me that the product management team will roll out the image resizing within tables for my site specifically. Not sure how that would work.

Tan Rong Wei. You are correct. Atlassian was concerned that users found resizing images too difficult, so it included almost no control for images in regular parts of a page and even less control for images in tables and layout panels. All you can do is insert a centre-aligned image into a table or layout panel.

You no longer need to waste time adjusting an image to the size you want. Instead, you can accept the size Atlassian decides you must have, and you can use the extra time searching for a better editor.

So, any 'bug testers' here find out that you can't resize pictures using the grid snaps in table cells?

I put a picture in my table, and my mouse cursor just won't change to the resize icon.