Richard Gfeller - 2021-07-10

FYI - Stating it was Fixed in v3.2 is a mistake on my part. It was automatically populated as such when I submitted my ticket.