Thanks for helping me reframe my thoughts. I definitely don't want to call anyone's concerns unimportant.
More specifically, I view retros as a time to talk about improving the team, either through experimentation or doubling down on good practices. To that end, I'd want topics to be problems or shout outs.
Something like "how do we test credit cards" might be a sign of "our documentation isn't great and it slows me down" but it's talked about as a discreet item. Similarly "I haven't seen Jira used this way before" isn't a problem; maybe the underlying issue is "I don't understand how we use Jira" or "what we're doing causes a lot of paperwork"