He also put all hardware and software issues into the same sprint "to work as one team", except the hardware issues had very little to do with the software issues; also, the hardware people never updated their tickets, so each sprint just had the same 40-50 spam messages for which you had to create custom filters to avoid.
He also changed the issue sizing mechanism once in a while. So we'd have hours, t-shirts, and Fibonacci numbers (including some odd non-Fibonacci numbers that "seemed right").
I would always prefer a less feature-rich issue tracker with sane defaults.
Linear.app, GitHub Projects, post-its on the back wall of an antisocial project lead, anything other than Jira. It just attracts people who think "Category" is a good category.