Atlassian, there has been a lot of comments  regarding nested macros and how it is not supported in cloud. The recommendations provided does not really work for some of macros as they still end up being broken even without converting them to the new Cloud editor.

Personally, I have experienced this issue on a very large scale migration (Scaffolding macro had the most impact as it was heavily utilised by them) that almost resulted in the customer pulling out from migrating their Confluence DC instance to Cloud.

Unfortunately, we did not get much help from both the vendors or Atlassian as they kept on pointing fingers at each other and the message I got was that the client had to manually fix this prior to migrating to cloud (this would have been challenging considering that they have almost 15k pages impacted by the limitation).

I would like to know if there any plans to support this feature as more customers migrate to cloud?

+1. Our customer are impacted due to this limitation. Do you have any timeline for this request?

This is BEYOND frustrating and disappointing that this is not a feature. As some as said we are being forced to move from server to cloud where we have been developing pages for 10+ years and have used the features available at the time. This might be the feature that makes me move on from Atlassian unless some workarounds can be provided. 

This suggestion has been open for 4 years. Please make a statement: Are there plans to develop this or will it remain a proposal for the next 4 years? Due to the forced cloud migration, we have to find at least an administrative solution, i.e. rebuild our content without nesting, or wait until this is possible.

The hub of our systems documentation is based on pages using Live templates with Scaffolding and nested 3rd party macros. Without the ability to nest macros we loose functionality that is essential and will probably move us away from using Confluence at all. Investigating a workaround or a solution to this problem has been very time consuming and frustrating. Very disappointing.    

FYI: When migrating from Server to Cloud, your pages will be using the old editor in Cloud. The old editor does support nesting. However, some apps decided not to build in old-editor support to their Cloud apps and their macros may not work with nesting. This is especially true if the App has a conversion step (during migration or post-migration) - e.g. Scaffolding.

I don't know how many vendors have made the claim that nesting is not supported in Cloud, when this is 100% false. "New editor in Cloud does not support nesting of (most) macros." is way more accurate.

Our company heavily relies on this feature in our current Confluence Server instance. Not having this feature available in the new editor will impact a lot of our pages.

Atlassian closed https://jira.atlassian.com/browse/CONFCLOUD-68323 as "Won't Do" last week.

This bug is for nesting 3rd party (Connect) bodied macros, that other one is for nesting Confluence's bodied macros.  Atlassian's macros are not implemented with Connect so they are different problems with the same end-user effect.

@Alex Medved the point of this bug is that CONNECT macros cannot be nested.  Essentially all 3rd party macros are Connect macros.  The problem of nesting Connect macros is for both the old and new/fabric page editors.  Notice that Atlassian CAN nest some of their macros... because they don't use Connect... which is a problem in itself, IMO.

Lack of support for nesting bodied macros is something else... that is https://jira.atlassian.com/browse/CONFCLOUD-68323 Nesting bodied macros is ONLY a problem in the new/fabric page editor.  Works fine in the old page editor.  This is why nesting tables doesn't work anymore (in the new editor).

Here is an article my support team uses for the problem of lack of support for nesting of CONNECT macros: https://artemis.atlassian.net/wiki/spaces/SUP/pages/994213891/Connect+Macros+Cannot+be+Nested+in+Connect+Macros

Here is an article my support team uses for the problem of lack of support for nesting of BODIED macros: 

https://artemis.atlassian.net/wiki/spaces/SUP/pages/593887233/Bodied+Macro+can+t+be+nested+in+a+MultiExcerpt+Fabric+V2+Page+Editor

The solution (if there is one in the future) may address both problems but they are different problems.  My customers and almost everyone I talked to are having a hard time understanding the difference.  I think it is important for Atlassian to know that these are different problems.

sasha2 thanks for the heads up.