Thank you.
I confirm this is a bug. I apologize for the inconvenience.

We make sure this is fixed in the next update. Not having the date, though.
Here is the gh ticket to track
https://github.com/jsreport/jsreport/issues/1257