Feature Request: Bulk Table Alignment & Auto-Fit Column Width via Rovo AI
Product: Confluence Cloud
Feature Area: Rovo AI + Table Formatting
Summary
I would like Rovo AI to support bulk table formatting operations on Confluence pages — specifically:
Bulk table alignment change — Instruct Rovo to change the alignment (left / center) of all tables on a page at once.
Auto-fit column width to content — Instruct Rovo to automatically resize table column widths to fit their content across all tables on a page.
Use Case
I develop mobile games and have adopted a workflow where I write development specification documents in Markdown (.md) first, then pass them to Rovo AI to generate Confluence pages. This allows me to draft structured specs efficiently in a text editor before publishing them to Confluence.
A single specification page often contains 10–20 tables covering screen transition matrices, UI element definitions, state/condition tables, and change logs.
When Rovo AI generates a Confluence page from Markdown, all tables are created with default center alignment and uniform column widths. When I want to left-align tables for better readability of specification documents, or adjust column widths to match the varying content lengths, I have to manually modify each table individually. With 10+ tables per page, this is extremely time-consuming.
What I'd Like
The ability to tell Rovo AI something like:
"Left-align all tables on this page"
"Auto-fit all table column widths to their content"
The ability to specify table formatting in Markdown before conversion, and have Rovo AI carry those settings into the generated Confluence page:
e.g., <!-- table-align: left --> as a comment or metadata directive in the .md file
Rovo would then modify the ADF (Atlassian Document Format) properties of every table on the page in a single operation.
Why This Matters
Productivity: Adjusting 10+ tables manually takes significant time. A single AI command or a pre-defined Markdown directive would reduce this to seconds.
Workflow completeness: In the .md → Rovo AI → Confluence page pipeline, formatting adjustments are the only step that still requires manual intervention. If formatting could also be handled by AI, the entire workflow would be fully automated end-to-end.
Consistency: Ensures uniform formatting across all tables on a page without human error.
AI-assisted authoring gap: Rovo AI can already create and edit page content, but it currently cannot control table-level layout properties (alignment, column width). This is a natural extension of its capabilities.
Current Limitation
Confluence's ADF does not currently expose table-level alignment as a modifiable property, and colwidth attributes are static values that do not support "auto-fit to content."
Even if I specify formatting directives in Markdown before Rovo processes the content, these layout properties cannot be carried over into the ADF when the Confluence page is generated.
As a result, I must manually adjust table formatting every time a page is generated, which breaks the otherwise seamless automation pipeline.
Suggested Approach
Extend ADF to support a tableAlignment property (e.g., left, center, right) at the table node level.
Add an autoFit or fitToContent option for table column widths in ADF.
Enable Rovo AI to read and modify these properties when instructed by the user.
Enable Rovo AI to recognize table formatting directives (alignment, width) in Markdown source and apply them to the ADF output during conversion.
This would fully automate the Markdown-based specification authoring workflow with Rovo AI and Confluence, delivering a significant productivity improvement for anyone who works with table-heavy documentation. Thank you for considering this request.
Hi @hoshikawa_daisuke , this is a solid, detailed write-up, but the Q&A forum isn't where product suggestions get tracked or built, it's better placed on Atlassian's public issue tracker so it can actually be voted on and picked up by the product team.
Splitting it this way also means the ADF property request stands on its own even if the Rovo command layer takes longer, and other users hitting the same table formatting pain can find and vote it independently.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.