Custom Panels Reverting to Legacy Panel Macros?

Question

Disclaimer: I know this probably belongs in a bug report but the bug report website does not recognize my company URL for some reason, so I'm posting it here instead.

Summary: Cloud editor silently converts custom panels to legacy panel macros on publish, losing their background color in view mode

Steps to reproduce:

* Create a new page in the cloud editor. Insert a custom panel (/custom panel) and pick any background color from the panel's color picker. Publish — the panel renders correctly.
* Edit the page again, change one character of unrelated text (do not touch the panel), and publish.
* View the page.

Expected: the custom panel keeps its background color.

Actual: the panel renders with a default white background and default text color. Internally, the ADF custom panel node has been converted to a legacy panel macro (bodied-extension, com.atlassian.confluence.macro.core): the chosen color and emoji are preserved in the macro parameters (bgColor, panelIcon, panelIconId, panelIconText) but are not rendered, and spurious breakoutMode: wide / breakoutWidth parameters (values vary, e.g. 760 or 1800) are stamped on even though I've never touched any width-related setting. Clicking the panel in the editor now opens the legacy macro configuration (hex-code fields) instead of the panel color picker. The conversion does not revert.

Important observations:

* Standard panels (info/note/success/warning/error) are unaffected.
* Custom panels nested inside a layout section (including single-column), an expand, or a table cell are not converted — only top-level custom panels are. This suggests the publish-time breakout normalization only processes top-level nodes and "resolves" custom panels by demoting them to macros.
* Reproduced on multiple pages, including panels written via the public API in ADF-native form, which are then demoted by the next editor publish.

Impact: every editor publish of an affected page silently strips the styling from all top-level custom panels; heavily-formatted knowledge base pages degrade with no warning or undo path short of version-history revert. I also don't want to add a single-column layout everywhere I want to use a custom panel. Please help!

Brandi Guess · Answer

I have a user that is getting this behavior, but when I went into the same page and made a custom panel it did not replicate.  I am yet unsure of what the difference is, but something is definitely happening.

Katie Brennan · Answer

I'm experiencing the same behavior that Andrew reported; it's happening in both legacy pages that have been converted from a datacenter instance to cloud and in brand new cloud pages.

Jessica_j1vjtw · Answer

Hello @Andrew Chang

Thank you for the detailed information on the behavior observed in the custom panels and the steps to reproduce.

We tried following the steps, and we tried with emoji, no emoji, changing the custom color, not changing it, adding text and without text, all test on different created pages to make sure it wouldn't impact the steps to reproduce and see if there was a variable that could trigger.

On all of the variables and pages testing each one, we edited a second time and tried to change the text only below the panel, without touching it, as described.

We also tried with a dark mode, since we noticed this was something applied, in your screenshot.

In none of the tests, we were able to replicate the issue, so we are not sure if this a widespread issue, or missed any reproduce steps, or there is another factor that could be actually triggering it on your pages and not on our tests site(s).

About the URL link, it looks like you are not an admin for the site (for the account used to create this post at least), so this is why you are probably unable to create a support ticket, since only admins and authorized contacts (product admins and billing admin as well) are able to open a support ticket.

With that in mind, we would love to keep investigating this issue, since we can't reproduce it, but we would require to give a check on your pages to see if there is something different that could be causing it.

For that, we will kindly ask you to ask a site-admin to open a support ticket on your behalf, so we can check it together.

Regards,
Jessica