Is that a joke ?
Old (non-cloud) version was having this functionality, cloud version does not, there is ticket opened for over 3 years and nobody is working on it ? What are we paying for ?

Excerpt from a Table, and Expand in an Excerpt!

It is so frustrating to lose the functionality that we used to have.

people have given up. Nobody from Atlassian is looking at this issue. 
it was created in 2019 by a person no longer with the company. They have been "considering" it since 2020.

To be frank this is a semi ridiculous limitation after such a long time. How on earth does Atlassian and its marketplace partners expect that large corporate Confluence installations with tens of thousand of pages can migrate to the cloud.

As per the link below it will be a great help if there was a tiny tool that will convert the backups in Refine "content layout" macro from server to cloud. ie "rw-content-layout" to "rw-ui-layout-macro" 

https://help.refined.com/page/roadmap-cloud

Migration assistant (Refined for Confluence)

@timgragg, top marks for cunning 😂

It looks like you can only nest a single level of expands though. I tried adding more tables, but was unsuccessful.

I found an interesting work around within the UI:

Create an outer expander
Add a Table inside that expander.
Add an expander inside the top-left box.
delete the rest of the columns and rows.

(won't let me attach screenshot)

I really at least need to be able to put an expand section within an excerpt.  Without these abilities, it makes confluence more unmanageable, and considering that functionality used to exist this is a terrible experience for your customers.

It is crystal clear that this functionality is absolutely required as mentioned by everyone in the comments section.

Without this functionality, it is leading to sub-optimal workarounds and contributing to unnecessary overhead. The new editor should support interoperability between macros, otherwise what's the value in using Confluence Cloud?

Confluence has take a giant step backwards with this new experience. It is now extremely difficult to do basic things: nested macros, page templates, etc. Confluence used to be my go to for building vibrant and dynamic sites. However, this is more of a toy now for novice users only. PLEASE fix the many issues and bring back the ability to develop advanced pages. Lack of support for macro nesting is a show stopper!

Another team affected here...I was wondering if this was reported in 2019, there are more than 700 votes, why this has not been implemented yet?

We are in UAT for migration from Server to Cloud.  Our users are completely up in arms due to this missing and they work they will need to do to their pages once migrated.

Please advise on the path forward for this 

This makes our migration from server to cloud really hard because we are using this a lot, also in user macros.

I agree this feature is extremely important. I hope the devs can implement it soon Thanks!

why is this still not a feature??

We need expands to nest in panels. Please soon.

I need a simple way in the confluence cloud, to add the basic styles to the header row of the Expand feature.  

+1 from me on this. I want to be able to add a numbered list to an Expand inside the cell of a table.

This is badly needed. We have several pages on the legacy editor and we're not looking forward to updating to the new editor because of this loss of functionality. And, not only can we not nest macros in panels, we don't even have the same level of customization as we did before with on-premise. Please implement. And while you're at it, please reopen this: https://jira.atlassian.com/browse/CONFCLOUD-66752 because the current panels still lack the same level of customization that we had on server.

+1 — this feature is badly needed please and thank yooouuu

@Kieran Gray can you give us any commend about this issue please?

The absence of this feature is precisely the reason why I am still using the legacy editor four years after it was supposed to have been superseded.

@Kevin Gérard, it means people have given up. Nobody from Atlassian is looking at this issue. 
it was created in 2019 by a person no longer with the company. 

it's been over 3 years since you 'started working on this' 
i need the same exact usecase as Tim in previous comment 

(scroll ignore in combination with Page properties macro)

Not being possible to do this makes it enormously more complex for our users to create a clear and structured docuement based. 

please provide an update on this so we know what to expect in the near X months

+1 

We need this feature to nest "Confluence page property macro" in "Scroll Ignore macro" (from Scroll Word Exporter APP). Otherwise we are not able to provide placeholder data which should not be printed into the word file.

Hey Nikita - I am somewhat aware of the workaround but I do not think it would work for the case of having a standard Confluence excerpt inside a table cell. At some level the nesting always breaks in the new editor.

But even if it could work (again I am 90% sure it does not). Do we really need add-ons now (even if they are very good ones) to handle use cases that were normal before the breaking changes with the new editors?

Maybe I'm hit harder here than others coming straight from Confluence Server but this seems to break a lot of useful workflows that accumulated in the past 10+ years.

Hello Joern,

I guess, for your case Table Filter and Charts for Confluence will do as a viable workaround, offering Table Excerpt/Table Excerpt Include macros to serve your purpose, allowing your to re-use tables elsewhere on a page or different space and further combine the reference with your Page Properties report via Table Transformer macro. 

For better macro management and the ability to combine the nested macro with each other - we have developed the Table Toolbox macro, feel free to try it out as well.

Best wishes,
Nikita

Stiltsoft Europe team

Biggest problem for me here: cell content cannot be an excerpt.

Page Property Reports do not support excerpts but other reports (e.g. content by label or reports provided by other add-ons) support only excerpts. So I currently need to have an excerpt macro AND duplicate that excerpt content in the page properties.   

Nested bodied macros helps the users a lot in clean and readable structure. This has to come to new editor. It is a pity that it was available in legacy one but not in the new editor.

Love the new editor although I hate that it doesn't have feature parity with the legacy editor.  The biggest issue is this one...inability to nest expand macro in the excerpt.  I am having to duplicate all of my content when switching to the new editor.

+1

Kindly add this feature as it used to work on previous versions on Confluence. 
This feature is vital for every day usage and avoiding having duplicated information. 

Please add the expand on expand, we need this feature sooo bad

The best workaround is for teams to use the Legacy Editor until Atlassian resolves all outstanding bugs and missing features. When they launched their New Editor years ago, the MVP was missing so much functionality from the Legacy Editor it caused an uproar and Atlassian decided to keep the Legacy Editor around permanently, but hide it in the templates.

I recommend having your teams star it to bump it to the top of their templates list. If you are missing the Legacy editor template request it from Atlassian so they can enable it on your environment. You will be able to continue to use all the macros you're used to and it should resolve any broken macro issues.

Is anyone from Atlassian willing to answer this question?

It would be very helpful in gaining momentum to open bugs, etc.  In other words, how many votes do we need to get something fixed/changed?

 Question – what is the "Under Consideration" acceptance threshold? 

Andrew, it means people have given up. Nobody from Atlassian is looking at this issue. 

it was created in 2019 by a person no longer with the company. 

+1...

I've run into so many dead-ends while hunting for workarounds to seemingly normal things, like:

1. Using tabbing (apps) to display macros (and it's failed workaround of nesting a layout within an expand, which is why I landed here frustrated)
2. Adding content to a panel (or an app that provides a panel) so I can have a background that actually prints to PDF
3. Half a dozen other things I already forgot about, but all equally annoying

EDIT:  Wait, this thread on this page is a macro, and it's within a tab for filtering...

+1 we relied heavily on nested macros for page cleanliness

I'm surprised there are 'only' 428 votes for such a crucial feature. Does every vote represent 10 others? Should those be encouraged to vote too?

My page designs are not going to be easily fixed after moving to the cloud. The layout options do not help with the custom sections/columns that I was using. But I can work around that probably. What I cannot work around is the lack of nested macros (is that what is meant by "bodied"?). I have expands inside of panels and panels inside of panels, etc. This is so essential for a good design and reworking all my pages will be a nightmare without this feature.

Probably trying to address new parts of the market, instead, with confluence own whiteboard solution: 

https://www.atlassian.com/software/whiteboards

As if that space is not crowded enough.

Fixing the existing product does not get much budget, I guess. Just milk the cow.

We are evaluating bugs while trying to complete a cloud migration and there is a highly unsatisfying number of bugs and feature requests in this same state, aging and ignored. What are the developers putting their focus on instead of these necessary features?

I noticed just now that the ticket was opened in 2019, last decade.

And the last Status Update was on 13 March 2020

Nearly 3 years ago, I'd say there is little hope that Atlassian cares about our 120 comments here. ** 

Agreed!  We have been using these features for years to build beautiful documentation. The limited feature set in the Cloud version has ruined our existing pages and they will need to be entirely redesigned if this is not corrected.

Yes, we need these things. If the feature existed in Server, why would you possibly remove it from Cloud? And it's been sitting out there for ages. Every feature missing from cloud has a ticket out there and every one of them is being ingnored.

Ethan: What is the next step, when will the issue move to In Progress? 

Completed the survey, link for anyone who doesn't feel like looking further up https://ows.io/os/7y4nno5l.

Survey done. It seems that the questions of the survey mostly concerning the nesting of Atlassian items itself (macros, pics etc). I hope that the nesting of macros which come from other confluence apps are taken into account too! So for example I would like to put a long page property report into a table filter (stiltsoft: table filter and charts app), and all that I want to put into an expand macro for a handier page structure ...

Survey done. Voting in favor of bringing this feature back!

Thanks for this survey and the option to reach out to you, much appreciated! Just completed the survey.

I have completed the survey.

Is the implementation (or fixing) of this functionality still under consideration?

My actual question is, when can I expect to be able to use all these nesting types in my wiki pages again?

Hi all, I'm Ethan, a product manager working on the rich-text editor. I’m here to promote a quick survey I've shared in the Atlassian Community forums. We're seeking feedback on your satisfaction with the experience of nesting content in the editor. Nesting refers to the insertion of a type of content inside another type of content. e.g. being able to insert an expand inside another expand, among other examples.

Survey link: https://ows.io/os/7y4nno5l

The activity shouldn't take longer than 5-10 minutes to complete. Your response will help inform my team’s priorities with regards to improving this experience, and the relative importance of being able to nest some content vs others.

We may reach out to survey responders to chat further on this topic over a video call. Those who take us up on this offer will be reimbursed for their time with an e-gift card.

If you have any further questions or comments to share on this topic, feel free to reach out to my team and I via email, or my Calendly link below:

• Email: eyew@atlassian.com

• Calendly: https://calendly.com/eyew/30min 

There are no workarounds!

I cannot believe the elimination of these functions, usually with updates software gets better and more empowering for users, not the opposite.. With the "update", you have eliminated so many options, it's stunning.

This is a Blocker for my team. We are moving to the cloud right now, and will need to rework a ton of pages. This will be very time consuming and inefficient, will need to totally redesign the site throughout 2023.

When will it be implemented/completed? 

I have completed the survey. Is addressing the functionality issues under consideration?

When can we expect to use all these nesting types in our site again?

Any update?

Thank you Randy! You saved me the effort of reading through 109 old comments 😅

Only workaround I know of is to use the legacy editor (mentioned near the top of this ticket).  Unless your account admin has enabled the Legacy editor page template, you'll need to copy an existing page created with the legacy editor to get started.

Super surprised this isn't allowed in Confluence Cloud.

Anyone know of workarounds?

@Dmitri that's a good point.

I think it would be helpful to just know what to expect or not and just add a big "WON'T DO" with a summarised explanation. Even if it pains the customer, at least you'd be transparent and we'll know.

Are the three years and over hundreds of comments still not enough for Atlassian to consider fix this BUG?
When will be it fixed?
Are you planning to fix it?
Can you fix it?

I need the excerpt macro in a table. We have a Glossary as a table and I need to reuse the definitions on other pages while still keeping the Glosaery in the table view that the other users are used to.

Yes, echo this. This would solve a lot of clutter in our documentation

Numbered Headings macro also does not work in the cloud version with nested bodied macros, which is a pity as this is crucial for writing company standards and other documents that require numbering.

Its confused that through API can do nested expand but UI cannot. Please add it back. 

This is a very crucial feature . Please consider implementing it

The ability to use a Todo macro within a Note/Tip/Warning macro would be nice.  This doesn't seem to be possible at this time.  For example, if I use /note and then try to invoke /todo within the note body, the checkbox for the action item is always placed below the body of the note.  Neither cut-and-paste or copy-and-paste within the note body works.

I need this please!

Great decision! Thank you

Great to see this is under consideration again, and that we can vote for the issue. Thanks!

Can you (Atlassian) imagine how many customers you lost by ignoring this functionality for three years?

Unfortunately I can't vote on this ticket but I would if I could. We use the Multiexcerpt macro suite and face the same problem: Unable to use Multiexcerpt Include in tables 

Hey the new editor is preventing us from making pages that look good/useful. Why does Atlassian keep closing down issues for features that their users want and keep ramming down updates that are downgrades?

This breaks any hope of Confluence being a useful single source tool. Poor Form Atlassian.

Absolutely agree with the above comments, not allowing nested bodied macros is an absolute game breaker for us. At least allow a certain level of nested macros, it does not have to be hundreds, but at least one or two!

Until this is solved there is no way I will use the new editor. It's not even possible to put an image into a panel, for crying out loud. 

Without the full capabilities of adding macros and nesting objects within . We're going to have to migrate away from Confluence and dare I say it, to Sharepoint. 
Sharepoint is free for us as part of our licensing but we prefer Confluence Server even at the ever increasing cost for it!
However, Sharepoint Online has the one features we need most, where Confluence Cloud unfortunately does not. 

I'm still nostalgic to the old editing experience.

The excerpt macro can not be put into a table with the "new" editor. Therefore we have to duplicate our content, I thought this was against Confluence best practices.

Why is this closed?

Removing functionality should never be the answer. I'm very disappointed with the limitations that we are discovering with Confluence Cloud. It's hands down an inferior product to Atlassian Server and Data Center. It's super frustrating. And the engineers at Atlassian just shrug their shoulders and tell us that there is nothing they can do. "That's just how it is" is their standard answer. That and trying to blame the companies providing plug-ins. But those companies are at the mercy of Atlassian too and have their hands tied until Atlassian fixes the issues with their Cloud product.

Because it's hard work to bring it back!

Why is this closed?

This will help a lot to structure the document& I want to use this macro to manage common parts across the documents& As for me it will be helpful to manage all notification in 1 place and also show them on the different confluence pages.

This is much needed functionality for me.

Also looking for this functionality

The lack of parity for nested macros has fully soured my team on Confluence. 

please reopen. functionality is needed:  Macro's into table cells

I am also looking for this functionality

I'm also looking to have this functionality.

I desperately need this to work especially the expand in an excerpt. How do we get it reopened? 

Our team is also looking for the options of having nested macros, specifically expand macro.

Your documentation says that this feature is available: "Nesting your Expand macros. You can put one Expand macro inside another, and Confluence will correctly show and hide the contents of all Expand macros, including the nested ones." (https://confluence.atlassian.com/doc/expand-macro-223222352.html#ExpandMacro-Changethemacroparameters). I wish that was true. Why did you close this much-requested Jira ticket with a "Won't do"? See https://community.atlassian.com/t5/Confluence-questions/Nesting-one-expand-macro-in-another/qaq-p/1147975, an issue that is wrongly marked "Solved," since the accepted solution is a 3-year-old promise from Avinoam to implement it, which he never did.

I can no longer vote on this. We are unable to migrate over to the cloud if this is not resolved. When is the ETA on this being resolved?

Our team is still looking for the ability to embed Excerpt macros within Expand macros and vice versa.

Was used a lot on our pages, can you please give feedback ?

We are also experiencing issues. Namely it does not seem to be possible for us to nest a 2-column layout within an expand. It would be wonderful if this could be addressed in the future!

Good news: Atlassian does listen!

In the last few days, quite some changes have been brought to the Confluence Cloud editor, most notably:

• position controls for images (left, right, center, with text on the right or left)
• keyboard shortcuts - apparently, Atlassian found a way to distinguish between (left-ctrl, left-alt) and (right-alt = AltGr) which makes their keyboard shortcuts for headings, lists, normal text and many others work again.

Kudos to Atlassian for this.

Now, there are just a few (very serious) performance problems in general and issues in table formatting. I have been assured that they are on Atlassian's radar, but not to be expected in the near term future. That is not good, but seeing that the problems are seriously researched and solved for good is helping a lot.

My frustration with Atlassian grows quite substantially these days:

• First, you put a gun to our head by announcing price increases for Server licenses and the discontinuation of the Server software line,
  forcing us to move into your cloud
• In the cloud you provide painfully slow and error prone service
• ... and go ahead to tout a "new latest and greatest editor" that is in Comparison to the Server editor akin to Microsoft NotePad compared to NotePad++.
  Is it really progress if we have to rewrite everything (or more to the point, restructure and rewrite) when we switch to the newest top of the line product?

I wonder where Atlassian customers are shoehorned to next.

Sorry to say so, but this should be a blocker. Our documentation (on server version) has about 2000 pages and we standardly structure them with nested macros - for example column in section macros, tabs in tabs, table in table, report charts in expands etc. As far as I understand it, I am not the only one who gets into trouble (look at the number of users who voted for the ticket!). Especially for professional writers who need a useful standard structure this is a no go. How can I migrate with our documentation from server to cloud without losing much of the quality I have been working for for years?

I share the same frustration as Andrzej.  Now our documentation will have to be re-authored to make it consistent.

I am with you all in the frustrations.  The new editor has made things more difficult in terms of making effective pages.  And I really like/needed the nestling as it made the pages cleaner.  It's already hard trying to make pages clean and less busy w/the lack of macros, and now to delete some or change the function of the macros, such as this one, just kills me.

This is extremely frustrating after migrating from on premise confluence where this was possible - I can't combine numbered list with code macro or note/info/warning macro.