I set up the SonarQube JIRA integration plugin on my system and restarted the server. After that I configured my build script with these settings:
sonar.jira.url (using HTTP)
sonar.jira.login.secured
sonar.jira.password.secured
sonar.jira.url.param (pointing to a JIRA filter)
sonar.jira.project.key (matches the prefix used in our JIRA tickets)
When I check the dashboard, the JIRA widget displays data from my filter correctly. However, I cannot find the “Link to JIRA” option in the “More actions” dropdown menu where it should appear.
I have tested this setup on SonarQube versions 3.0, 3.4.1, and 3.5 but the link option never shows up. The plugin seems to be working since it pulls JIRA data, but this specific menu item is not there.
Had the same issue on 3.4.1. The problem was with the sonar.jira.url.param config. Your JIRA filter URL needs to work without authentication and return valid XML when you hit it directly. I found that even when the widget works fine, the link functionality needs different access levels. Try making a public filter or enabling anonymous access, then test the URL in your browser before adding it to config. Also check if your SonarQube user can actually create JIRA links - reading data isn’t enough.
This usually happens because of incomplete plugin setup, not permissions. I had the same problem on version 3.5 - the widget worked fine but the menu option was missing. Turned out I was missing the sonar.jira.issueassign.login parameter in my build config, or it was formatted wrong. Without that setting, SonarQube can’t connect properly to create new issue links, even though it reads existing data just fine through the widget. Also check that your JIRA instance has REST API enabled and your SonarQube server can reach it. The plugin uses different API endpoints for showing data vs creating links, which is why one works and the other doesn’t.
yea, i think it could be a permissions thing too. i struggled with that before - jira was pulling data, but links? nope. double check your permissions and make sure there ain’t any project limits in place that’s stopping it.