Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,030
Community Members
 
Community Events
184
Community Groups

User macro not working as expected after version upgrade and DataCenter migration

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?

1 answer

0 votes
Matt
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 26, 2023

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}"

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events