March 2025

🔍 Summary

March prioritized user experience consistency and improved template debugging. Admin visibility was enhanced with better navigation, while developers gained more feedback for rendering issues and clearer variable handling in Velocity.

✨ New Features & Enhancements

• Smart “Save” Button Logic
  The Save button in macro edit mode is now context-aware: it remains inactive until changes are detected, reducing accidental submissions and unnecessary API calls.

  

• New Admin Navigation via Apps Menu
  Added a dedicated entry in the Confluence “Apps” menu (visible to admins only), linking directly to the User Macro (UM) configuration page. This improves discoverability and speeds up access for admin users.

  

• Dynamic Macro Body: Plain-Text Option
  Introduced a plain-text body option for dynamic macros under the Settings tab, giving creators more control over rendering formats when HTML or rich-text is unnecessary.

• Auto-Fill for Optional Parameters
  Non-required user parameters are now explicitly set to empty strings instead of being left as null, avoiding warning banners and reducing confusion during macro use.

🛠 Bug Fixes & Improvements

• Fix: No Feedback on Template Rendering Errors
  Improved error visibility when macro templates fail to render. Users now receive a clear error message if their template contains syntax or logic issues, making debugging faster and less frustrating.

• Fix: Variable Parsing Without Brackets
  Corrected a Velocity behavior where string interpolation failed without curly braces. For example, using ${spaceKey} is now required and properly documented in context-sensitive hints.

Curly brackets must be used only if variable has these symbols right after it:

• alphabetic (a .. z, A .. Z)

• numeric (0 .. 9)

• underscore ("_")

In all other cases it can be user without curly brackets