This plugin integrates Atlassian JIRA to Jenkins.



This plugin has an optional feature to update JIRA issues with a back pointer to Jenkins build pages. This allows the submitter and watchers to quickly find out which build they need to pick up to get the fix.

JIRA Issue links in build Changelog

When you configure your JIRA site in Jenkins, the plugin will automatically hyperlink all matching issue names to JIRA.

If you have additionally provided username/password to JIRA, the hyperlinks will also contain tooltips with the issue summary.

Updating JIRA issues with back pointers

If you also want to use this feature, you need to supply a valid user id/password. If you need the comment only to be visible to a certain JIRA group, e.g. Software Development, enter the groupname. 

Now you also need to configure jobs. I figured you might not always have write access to the JIRA (say you have a Jenkins build for one of the Apache commons project that you depend on), so that's why this is optional.

And the following screen shows how JIRA issue is updated:

By taking advantages of Jenkins' fingerprint feature, when your other projects that depend on this project pick up a build with a fix, those build numbers can also be recorded in JIRA.

This is quite handy when a bug is fixed in one of the libraries, yet the submitter wants a fix in a different project. This happens often in my work, where a bug is reported against JAX-WS but the fix is in JAXB. 

For curious mind, see this thread for how this works behind the scene.

Referencing JIRA Release version 

To reference JIRA Release versions in your build, you can pull these releases directly from JIRA by adding the JIRA Release Version Parameter. 

This can be useful for generating release notes, trigerring parameterized build, etc.

Generating Release Notes

You can also generate release notes to be used during your build. These notes can be retrieved from an environment variable. See the Maven Project Plugin for the environment variables found within the POM.

After your build has run, you can also have the plugin mark a release as resolved. This typically will be a release you specified in your Build Parameters.

The plugin can also move certain issues matching a JQL query to a new release version.

Sample usage of generated Release Notes:

JIRA Authentication & Permissions required

Note: As a rule of thumb, you should be always using a service account (instead of a personal account) to integrate Jenkins with JIRA.

Make sure that the JIRA user used by Jenkins has enough permissions to execute its actions. You can do that via JIRA Permission Helper tool.

JIRA Cloud

In Atlassian JIRA Cloud, it's not possible to create a user without an email, so you need to create API token.

Then create a global Jenkins credential, where you put Atlassian ID email as username and API token as password.

You can check if your API token works correctly by getting a correct JSON issue response with this command (where TEST-1 is an example issue in your project):

$ curl -X GET -u <email>:<API token> -H "Content-Type: application/json"  https://<YourCloudInstanceName>.atlassian.net/rest/api/latest/issue/TEST-1

Also make sure that CAPTCHA is not triggered for your user as this will prevent the API token to work - see CAPTCHA section in Atlassian REST API documentation.

System properties

Property Name

Functionality Change


Use to disable resolving user email from JIRA usernames. Currently there is no option for this in UI.

Related Resources


Version 3.0.9 (2019-08-21)

Version 3.0.8 (2019-06-28)

Version 3.0.7 (2019-05-01)

Version 3.0.6 (2019-03-30)

Version 3.0.5 (2018-11-07)

Version 3.0.4 (2018-10-26)

Version 3.0.3 (2018-10-16)

Version 3.0.2 (2018-09-25)

Version 3.0.1 (2018-08-22)

Version 3.0.0 (2018-05-20)

Version 2.5.2 (2018-05-04)

Version 2.4.2 (2017-08-08)

Version 2.4 (2017-08-03)

Version 2.3.1 (2017-05-23)

Version 2.3 (2016-12-19)

Version 2.2.1 (2016-03-26)

Version 2.2 (2016-02-20)

Version 2.1 (2015-11-18)

Version 2.0.3 (2015-10-26)

Version 2.0.2 (2015-09-15)

Version 2.0.1 (2015-09-10)

Version 2.0 (2015-09-02)

Incompatbile change: switch from JIRA RPC SOAP to JIRA REST API communication - the former has been deprecated and dropped since JIRA v.7.0. 

Version 1.41 (2015-06-10)

Version 1.39 (Oct 6, 2013)
Version 1.38 (Aug 23, 2013)
Version 1.37 (Jun 21, 2013)
Version 1.35 (Jul 29, 2012)
Version 1.34 (Jun 11, 2012)
Version 1.33 (Jun 1, 2012)
Version 1.32 (May 15, 2012)
Version 1.31 (May 1, 2012)
Version 1.30 (April 25, 2012)
Version 1.29 (August 25, 2011)
Version 1.28 (Jun 15, 2011)
Version 1.27 (Feb 27, 2011)
Version 1.26 (Jan 14, 2011)
Version 1.25
Version 1.24
Version 1.23
Version 1.22
Version 1.21
Version 1.20
Version 1.19
Version 1.18
Version 1.17
Version 1.15 (2008/08/22)
Version 1.13 (2008/08/05)
Version 1.12
Version 1.11
Version 1.10
Version 1.9
Version 1.8
Version 1.7
Version 1.6
Version 1.5
Version 1.4