This plugin integrates Atlassian JIRA to Jenkins.

First, you need to go to Jenkins' system config screen to tell Jenkins where's your JIRA. 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. 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. 

Starting from this plugin version 2.0, it is using JIRA REST API to communicate instead of JIRA RPC SOAP which has been deprecated and removed since JIRA v.7.0.
If you have an older JIRA version and still want to use JIRA RPC SOAP, do not upgrade the plugin.

JIRA RPC SOAP access configuration 

NOTE: This applies to plugin version < 2.0 and JIRA version < 7.0.

JIRA also needs to be configured for Jenkins to remotely login.

Go to the general configuration screen and enable remote API calls. Again, this is only needed if you use the abovementioned optional feature, and if you forget to do so, Jenkins will nicely warn you.

With that, JIRA keys in changelogs are now hyperlinked to the corresponding JIRA pages (complete with tooltips!)

Updating JIRA issues with back pointers

To have Jenkins update JIRA issues with back pointers to builds, 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

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.

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 2.0 (September 2015)

Version 1.41 (Jun 10, 2015)

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