You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey Atlassian project managers,
You removed the support of nested tables in Confluence cloud, so we can't create anymore tables in a list or in another table for example....
Please tell us why you removed this feature ? If you write documents, this is used a lot, don't you know about this ? Maybe you use another software ?
I don't thank you, really.
odd that it was changed...the above is a poor workaround. would be interested in hearing the Atlasssian approach for this newly added 'feature'.
I have another approach using the Multiexcerpt macro:
In the example below "Notes" is the page where I create the individual tables, each surrounded by a MultiExcerpt and a title that explains where it goes.
Next, use the Multiexcerpt include macro and insert it the correct data into the into the main table
Save the page and it looks like this:
I hope that this helps.
Thanks Michael, this was the best workaround I found (till Atlassian decides to fix this mess) reading all other comments in this and many other threads related to this problem.
I however used the Excerpt and Excerpt Include macros.
Thanks for all the workaround.
But be honestly. This is just a bad change.
It makes confluence a bad tool for creating any detailed technical documents. You have to spend lot of time just try to make the layout more readable ? But you can do this in seconds with words or google doc...
Just wonder what is the road map of Confluence?
We used to use Confluence build detailed technical documents. But we can no longer do that.
It just silly if we need other tools to write documents then put them into Confluence.
An additional workaround that I don't believe is described above:
If you have the Source Editor plug-in installed, you can use it to copy and paste the source code of the sub-table into the main table.
It'll look something like this (I did not include the full table formatting for brevity) :
<p>Provide basic concept info:</p>
<td colspan="1">Content 1</td>
<td colspan="1">Content 2</td>
Note: Confluence Cloud does not play nicely with the Source Editor plug-in, even though it is supposedly supported. Confluence will automatically inject gross spacing formatting if you dare to open the normal editor functions after making adjustments to the source code.
Removing nested tables is a blockheaded decision at best. Structure in a HTML document comes from nested tables. No nested tables? No structure. Yeah, fallback to bulleted lists or something? Nope.
Don't bore me with "workarounds" when it's hard to make people even start using Confluence in the first place.
This is the situation of a manufacturer deciding to remove the wheels from a wheelchair because these are then easier to implement, test and paint in silly colors.
Once UX designers and "focus groups" are ensconced in a decision process, it's over I guess. Oh yeah, that reminds me. That "flat look" is fugly. Just saying.
Put your data in an excel spread sheet and use the Office Excel macro to include it on your page?
Aside from trying to keep data single-sourced in Confluence, what happens when either the owner of the Excel file leaves without transferring owners or your company wants to move from Office to Google?
The spreadsheet file has to be uploaded/attached/included on the Confluence page so as long as someone has edit permissions on the page, ownership shouldn't be an issue. Granted, editing it is more cumbersome than editing a Confluence page/table directly.
Google Sheets can be downloaded as .xlsx files and then uploaded to Confluence.
Unfortunately I'm not working with the cloud product, so I can't try out solutions. My env is enterprise server. But this has me intrigued since I do nest tables and would get hammered if my env gets moved to the cloud.
So dumb question. Have you tried creating the child table in an included macro like Panel, Excerpt, Page properties, Section/Column (either or combined), Indent, TOC Zone and then move that macro into the cell in the parent table?
All these worked for me in server and Column (sans Section) and Page properties minimized white space around the child table. Of course the table greatly expands when editing due to the included macro(s).
This is a very bad product decision. We are moving to the Cloud version and use nested tables heavily in EVERY page.
I can't see any of the workarounds being a replacement for (quick) editing.
Since posting my workaround above using excerpts to nest tables, our Confluence instance has been updated and we're now using 7.8.3. In this version I'm able to nest tables to my heart's content by simply adding a table inside the cell of another table. No workarounds necessary! Not sure when this behavior changed but I'm glad it is now simple to do.
I should note that we're using the server edition.
About an hour a go I added a comment about how bad it is that Confluence does not support nested tables. After using Confluence for a bit I realized that when I had nested tables the nested table was always in column 2. To get around it I took the info in column 1 and called it a heading then added the table in column two under the heading. Not for everyone but it seems to work for me. I just looked at what I did in a few hours with Confluence and am quite proud of what I have created. My first Wiki. Thanks Confluence!!!
OMG - would it not be just easier to bring back the ability to just create a table within a table? What purpose did removing that ability have, even within the context of the New & "Improved" editor?
I insisted on having Confluence at my new job as I relied on it so much at my last one, but honestly these improvements may turn out to be dealbreakers for me
I completely agree. I am trying to move a template to a different space which you cannot do either, which seems like a poor design not having this feature, you can move pages to other spaces, why not a template, and it has nested tables. We have been using this template for years and now because we are reorganizing we cannot have a new template with nested table to match the existing template.
Atlassian - Is there ever going to be a fix for this issue? Or what is your best solution to this issue?
Amazing the sort of stuff that gets removed. Guess some UI expert knew better than us simple users...