Issue Summary

Roadmap Planner macro content is pruned and fails to render when linked to pages with special characters in titles.

Steps to Reproduce

1. Create a Confluence page with a title containing special characters (e.g., Changekategorien SmartPCN --> Verteilerschlüssel R&S).
2. Create a second page and insert the Roadmap Planner macro.
3. Within the Roadmap Planner, create a bar and link it to the page created in Step 1.
4. Save the page (the macro should render correctly initially).
5. Open the page in the Editor or use the Confluence Source Editor plugin to view/edit the source.
6. Save the page or close the source editor.
7. Observe the Roadmap Planner macro on the published page.

Expected Results

The Roadmap Planner macro should correctly escape special characters within its JSON parameters and maintain its configuration (bars, lanes, and links) across edits and storage format transformations.

Actual Results

1. The macro fails to render, often displaying an error or appearing blank.
2. In the page Storage Format, the macro is pruned to a single self-closing tag (e.g., <ac:structured-macro ac:name="roadmap" ... />), losing all nested <ac:parameter> data.
3. Confluence logs show a NullPointerException wrapped in an XhtmlException:
   Caused by: java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because the return value of "java.util.Map.get(Object)" is null at com.atlassian.plugins.roadmap.TimelinePlannerMacroManager.lambda$findRoadmapMacroDefinition$1

Workaround

Rename the linked Confluence pages to remove special characters (specifically &, <, and >) before linking them within the Roadmap Planner macro. If the macro has already been pruned, it must be recreated after the page titles are updated.

Security Level

None

Component

Editor / Macros

Severity

2 - Major (Data loss within the macro configuration)