I installed the SonarQube JIRA integration plugin and restarted my server. Then I configured these settings in my build configuration:
- jira.server.url (using HTTP protocol)
- jira.username.secured
- jira.userpass.secured
- jira.filter.parameter (pointing to a specific JIRA filter)
- jira.project.identifier (matches the project prefix in JIRA ticket IDs)
After running the code analysis, the JIRA dashboard widget displays data from my configured filter correctly. However, when I click on the actions dropdown menu, there is no “Link to JIRA” option available. I have tested this setup on SonarQube versions 3.0, 3.4.1, and 3.5 with the same result.
Has anyone experienced this issue before? What configuration might I be missing to make the JIRA link appear in the actions menu?
I’ve hit this exact issue before. It’s usually a plugin version mismatch. The JIRA integration plugin has specific versions for each SonarQube release, and the actions menu breaks even when widgets work perfectly. Make sure you’re running the exact plugin version for your SonarQube build - don’t use a newer plugin on an older instance. I did that once and got the same problem: data loaded fine but all the linking features disappeared. Also check if your jira.server.url is actually reachable from the SonarQube server, not just your browser. The linking makes server-side calls that fail silently if there’s network issues.
check your sonar logs when you hit that menu - there might be a hidden error getting thrown. ive seen this before where the widget loads fine but actions fail due to bad jira urls or ssl cert issues. try switching your jira.server.url from http to https too.
Had the same issue - it’s probably a permissions problem, not configuration. Your widget shows data fine, but the linking option needs specific JIRA permissions. Check if your JIRA account has ‘Link Issues’ permission for that project. Also, make sure your SonarQube user has ‘Administer Projects’ permission. Mine was reading data just fine but silently failing on write operations because of missing permissions. Test it with a JIRA admin account first to confirm that’s what’s happening.