Generally speaking it’s worth noting that tracking SonarQube issues into Jira is not something we (at SonarSource) consider as a good practice. There’s a good insight on this in this blog post: Stop planning; fix the leak!. It dates back from 2 years, so the details are maybe not up-to-date, but some essential pieces remain:
Let’s say you’re using JIRA in your company. When you link an issue to JIRA, the SonarQube integration automatically creates a ticket for that issue. So if you want to keep track of 100 issues, you’ll end up with 100 JIRA tickets that aren’t really actionable (you just have a link back to SonarQube to identify every single issue) polluting your backlog. What’s even worse is that when an issue gets fixed in the code, it will be closed during the next SonarQube analysis, but the corresponding ticket in JIRA will remain open! Anyway, issues in the SonarQube server and tickets in JIRA just don’t have the same granularity.
And in some special cases where you still wish to create one Jira ticket for addressing a bunch of specific tickets, then I would recommend tagging these issues with a common tag, that way you can link them all at once, and reference that in your Jira ticket.