Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


When will nesting an expand into another expand be made available on confluence cloud?

There was a question posted in 2019 about the need for this. The original accepted response was:

We're currently in the process of redesigning a new experience for the expand macro which will allow it to both nest and work seamlessly on any device. 

We'll absolutely let you know once it's live!

Sadly, that response was made in August of 2019 and has yet to come true. We're now coming up on three years without this feature. The PM who posted the original response hasn't had any activity in the Atlassian community since January of 2020 and was last active in May of 2020. I've decided to post the question again in hopes of a meaningful response.

I gave an answer to that post (which I will link below) which shows that nesting expands is possible, we just don't have UI functionality for it. Is this something that is on the roadmap that we can look forward to? This was a feature on Jira server that I myself, and I'm sure many others, used fairly heavily. I also believe that users of the cloud version without prior experience in this feature would also love it and get a benefit from it's existence.

Original post:

Solved: Nesting one expand macro in another (

My Solution: 

The functionality is still there on the cloud side, it's just not existent in the editor. If you build pages dynamically using the APIs or have post-processing done via API calls to generate the pages, you can nest your expands. Below is a sample API call. In the below example, replace the items in double square brackets [[]] with your own content. It still needs to be added to the editor itself, and this is far from a perfect approach, but it's the only option right now that I can see as feasible. If you attempt to use the cloud editor after using this method, you'll see the below error in sections you've used this work around.




            "value":"<ac:structured-macro ac:name=\"expand\" ac:schema-version=\`"1\`" ><ac:rich-text-body><h1>First Nested Level</h1><ac:structured-macro ac:name=\"expand\" ac:schema-version=\"1\" ><ac:rich-text-body><h2>Second Nested Level</h2></ac:rich-text-body></ac:structured-macro></ac:rich-text-body></ac:structured-macro>",

4 answers

1 vote
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Jan 09, 2024 • edited

I have come up with another solution:

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.Screenshot 2024-01-09 at 10.52.18 AM.png

It seems like they're finally looking into this issue again!  There's a Jira ticket last updated on 06 Oct 2022 that's Unresolved and Under Consideration.  Hopefully, that means there's good news coming soon.

For my nested expand pages, I am waiting for a solution before converting to the new editor. Please re-introduce this functionality!

Is the nested expand feature enabled in confluence? This is a basic feature that should be available in confluence page. 

Where can I find/check/set that?

Don't you love it when something sold to you as an upgrade is really a downgrade. Features seem to be lost left and right

Stuff like this is a piece of cake in Notion

This is also receiving some more attention because of Bring back the option to add macros within a numbered or bulleted list which was something one could do in previous versions and depends on Nest Expand or other Bodied Macros in another Macro to be implemented

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events