JiraTestResultReporter Jenkins插件无法自动创建问题

Let’s break down why your auto-issue creation isn’t working even though manual creation works (great sign that the Jenkins-Jira connection is solid!). Here are the most likely fixes to check:

1. Don’t forget job-level plugin configuration #

It’s easy to set up global Jira credentials and toggle "Auto Raise Issues" in system config, but many plugins require you to enable the same behavior per job too. Head into your Maven project’s configuration page, find the JiraTestResultReporter section, and double-check that the option to automatically create issues for failed tests is checked here as well. Sometimes the global setting doesn’t propagate to individual jobs by default.

2. Ensure test reports are being generated correctly #

The plugin relies on reading your test results to know which cases failed. Make sure your maven-surefire-plugin is properly configured to generate XML reports (the default behavior, but worth confirming). Check the build logs for any warnings about missing test reports or failures to parse them—if the plugin can’t find the failed tests, it can’t create Jira issues for them.

3. Verify plugin and platform compatibility #

Outdated or incompatible plugin versions are a common culprit. Check if your JiraTestResultReporter version is compatible with your Jenkins instance and Jira version (Cloud/Data Center). Try upgrading the plugin to the latest stable release, or if you recently upgraded, roll back to a version that was known to work with your setup.

4. Check build step order and trigger conditions #

Make sure the plugin is running after your Maven test step finishes. If the plugin tries to process results before tests run, it won’t find any failures. Also, look into any filtering rules you might have set up—some plugins let you limit auto-issue creation to specific branches, new failures only, or certain test packages. If your failing tests don’t match these rules, auto-creation won’t trigger.

5. Dig into Jenkins logs for hidden errors #

Manual creation works, but auto-creation might be hitting a silent error. Head to Manage Jenkins → System Log and search for logs related to JiraTestResultReporter. Look for exceptions about missing fields, invalid issue templates, or permission quirks (even though manual works, the Jenkins service account might have different context than your user account for auto-runs).

6. Validate your Jira issue template #

If you’re using a custom template for Jira issues, make sure all required fields are being populated correctly. For example, if your Jira project requires a "Component" field but your template doesn’t set it, auto-creation will fail silently (while manual creation lets you fill it in). Check that variables like ${testClass} or ${testFailureReason} are correctly mapped to Jira fields, and that the project key and issue type are valid.

内容的提问来源于stack exchange，提问作者srinivasb