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
Next: Root
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.
Server version before upgrade: 7.13.7
Data Center version: 7.19.8
Previously, we had this code and everything worked fine:
## @noparams
$action.dateFormatter.format($content.currentDate)
That displayed the format DD-MMMMMMMM-YYYY. Ex: 25-May-2023
After the migration, we found that the user's macro does not display anything, just "$action.dateFormatter.format($content.currentDate)". Just show the date with:
## @noparams
$content.currentDate
That displays the following format: Thu May 25 12:46:42 CEST 2023
Can anyone figure out this conundrum?
You're hitting this known bug, sorry "feature" :-) : [CONFSERVER-82741] Variables in user macro are not resolved - Create and track feature requests for Atlassian products.
There's a workaround or you can try to upgrade to 7.19.9.
Given the code in your user macro, this flag should work:
CATALINA_OPTS="-Dmacro.required.velocity.context.keys=action,req,content ${CATALINA_OPTS}"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.