Popular Content macro issue with timeframe parameter value of 1d

[linde-engineering-uk]

Dear all,

we are running Confluence 5.9 (server, not cloud) and recently stumbled about a strange issue of the Popular Content macro:

The desired timeframe of the Popular Content macro should be one day, so we provided the parameter value "1d". Then we were wondering about the high results after some tests we found out that the macro seemed to fallback to the default parameter value of one week ("1w"). Values such as "2d" and "3d" are working as expected but not "1d". We finally found the workaround to specify the desired timeframe as "1.0d".

At this point I would like to know if you ever ran in this issue too??

If yes, a general bug is very likely and should be raised to Atlassian...

Thank you in advance,
Uwe

[AnnWorley]

I found an existing bug report for the behavior you are experiencing. Thanks so much for the workaround, I added it to the bug report:

Popular macros returns same results for 1d and 1w