Skip to end of metadata
Go to start of metadata

Plugin Information

View JIRA on the plugin site for more information.

Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

This plugin integrates Atlassian JIRA to Jenkins.


TOC:

Using JIRA REST API

First, you need to go to Jenkins' system config screen to tell Jenkins where's your JIRA.

On JIRA side, there is no action necessary as the REST API is enabled by default.

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.

Incompatible change

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.

Using JIRA RPC SOAP (deprecated)

NOTE: This connection type is only supported in plugin v. 1.41 and lower.

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!)

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 Permissions required

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.

  • For creating JIRA issues, the user has to be able to Create Issues in the specified project
  • If you additionally enter assignee or component field values, make sure that:
    • both of the fields are assigned to the corresponding JIRA Screen
    • the JIRA user is Assignable in the project
    • the Jenkins JIRA user can Assign issues

System properties

Property Name

Functionality Change

-Dhudson.plugins.jira.JiraMailAddressResolver.disabled=true

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

Related Resources

Releases

Version 3.0.5 (2018-11-07)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Version 3.0.4 (2018-10-26)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Version 3.0.3 (2018-10-16)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Version 3.0.2 (2018-09-25)

Fix security issue

Version 3.0.1 (2018-08-22)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Version 3.0.0 (2018-05-20)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Version 2.5.2 (2018-05-04)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Version 2.4.2 (2017-08-08)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Version 2.4 (2017-08-03)

T Key Summary Status
Loading...
Refresh

Version 2.3.1 (2017-05-23)

T Key Summary Status
Loading...
Refresh

Version 2.3 (2016-12-19)

T Key Summary Status
Loading...
Refresh

Version 2.2.1 (2016-03-26)

T Key Summary Status
Loading...
Refresh

Version 2.2 (2016-02-20)
  • Split each SCM changes in paragraphs
  • support release candidates (RCs) via Maven ComparableVersion
  • Console logging improvements in various places
  • JiraEnvironmentVariableBuilder support
  • Support adding labels to updated issues
  • (optionally) add scm entry change date and time to description in JIRA tickets

Also the related tickets were fixed:

https://issues.jenkins-ci.org/issues/?jql=labels%3Djira-plugin-2.2

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Version 2.1 (2015-11-18)
  • Bumped Jenkins Core to LTS v. 1.609.3
  • Added dependencies: mailer-plugin, matrix-plugin
  • Removed dependencies: maven-plugin

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Version 2.0.3 (2015-10-26)

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Version 2.0.2 (2015-09-15)

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Version 2.0.1 (2015-09-10)

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

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. 


T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Version 1.41 (2015-06-10)

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Version 1.39 (Oct 6, 2013)
  • Ability only to comment issue without processing of workflow (pull #38)
Version 1.38 (Aug 23, 2013)
  • Post build step to create new JIRA version (pull #30)
Version 1.37 (Jun 21, 2013)
Version 1.35 (Jul 29, 2012)
  • Prevents multiple comments on one issue for matrix builds. (PR #13)
Version 1.34 (Jun 11, 2012)
  • Fix NPE when Jenkins user does not have access to perform any workflow actions JENKINS-13998
Version 1.33 (Jun 1, 2012)
  • Support workflow steps as build actions and/or post-build notifiers JENKINS-13652
Version 1.32 (May 15, 2012)
  • Option to show archived versions.
Version 1.31 (May 1, 2012)
  • Add JiraIssueMigrator - a post build action that will move issues to a new fixVersion based on a JQL query.
  • Add Additional filtering of issues to be included in the release notes. Defaults to 'status in (Resolved, Closed)'
Version 1.30 (April 25, 2012)
  • Add build parameter that providers a drop-down with JIRA release versions
  • Add a build wrapper that will assemble release notes based on issues in the release version and store it in an environment variable

        # Issue Type
        - [JIRA-123] Issue summary
        - [JIRA-124] Another Issue summary
        # Another Issue Type
        - [JIRA-321] Yet another issue summary
    
  • Add a post-build action that will mark a version as released in JIRA
Version 1.29 (August 25, 2011)
  • JENKINS-10817 Jira-plugin should add the overall build result to the issue's comment
  • Include revisions also for non-subversion plugins; include revisions also if we don't have a repository browser
  • Defined a new parameter type for parameterized builds that allow you to select a JIRA ticket (from the result of a JQL query)
Version 1.28 (Jun 15, 2011)
Version 1.27 (Feb 27, 2011)
  • Updates for Jenkins
Version 1.26 (Jan 14, 2011)
  • (JENKINS-2508) : JIRA plugin not updating JIRA when perforce plugin used.
Version 1.25
  • (JENKINS-6758) : Failed to save system settings with JIRA Plugin.
Version 1.24
  • (JENKINS-6462) : Version 1.355 of Hudson and Jira Plugin 1.21: Images in Jira comments are not showing up.
Version 1.23
  • (JENKINS-6264, JENKINS-6282) fixed : IndexOutOfBoundsException when no issue pattern is configured (default pattern wasn't used)
  • (JENKINS-6381) fixed : configured patterned wasn't used for changelog annotation. Default pattern was always used for that.
  • improved default pattern to not match commit messages with dots in the number part (like 'projectname-1.2.3'). These messages are e.g. used by the Maven release plugin
Version 1.22
  • (JENKINS-6043) : Issue pattern can be configurable
  • (JENKINS-6225) : option to update jira issue whatever the build result is (even if failed)
Version 1.21
Version 1.20
Version 1.19
  • Fix: Prevent carrying forward invalid issue ids forever
Version 1.18
  • Case insensitive matching of JIRA ids also in the 'recent changes' view (JENKINS-4132)
  • fetch missing details for JIRA issues - i.e. completes issue title tooltip in 'recent changes' view (JENKINS-5252)
  • prevent build FAILURE if JIRA site is not available (JENKINS-3046)
Version 1.17
  • Fixed an ArrayIndexOutOfBoundsException when JIRA issues contain '$' in the name.
  • Support underscore in project names (JENKINS-4092)
  • Support digits in project names (JENKINS-729)
  • Case insensitive matching of JIRA ids (JENKINS-4132)
  • Don't strip JIRA id from posted comment
  • German translation
Version 1.15 (2008/08/22)
  • Update JIRA if the build is UNSTABLE or better.  Previously only updated if the build was stable.
  • Include relevant SCM comment in the JIRA comment which should make JIRA ticket history more meaningful.
Version 1.13 (2008/08/05)
  • Fixed a performance issue in a large enterprise deployment of JIRA (JENKINS-1703)
Version 1.12
  • A typo in the commit message shouldn't break builds (JENKINS-1593)
  • Postpone JIRA updates until a successful build is obtained (JENKINS-506)
Version 1.11
  • Added more logging and debug flag to examine issues that people are reporting (report)
Version 1.10
Version 1.9
Version 1.8
Version 1.7
  • Fixed NPE when username/password is not set (JENKINS-828)
Version 1.6
  • Relaxed the JIRA project key regexp a little bit to allow numbers (JENKINS-729)
Version 1.5
  • Issue hyperlinking is now smart enough not to be confused by strings that look like JIRA issue that actually aren't.
Version 1.4
  • Fixed a bug that prevented tooltips for JIRA issues from being displayed JENKINS-694

83 Comments

  1. It would be great if the pattern for the JIRA project key would be configurable so that non-standard project ID's could be matched.

    I think it's quite common to use numbers in project keys - especially if you have lots of projects.

    1. Please use the issue tracker for RFEs and bugs.

  2. Kohsuke,

     It would be nice if the Hudson Jira and Perforce plugins are integrated. In the project I'm working one, Jira and Perforce are integrated (using a standard plugin I believe), so a Perforce changelist is associated with a perforce job whose name matches a Jira issue. When I access the Hudson changes page, it shows the job name (for instance, JENKINS-2), but without a link to the Jira issue.

     I'm not sure if this is an issue on the Jira Plugin, Perforce Plugin, or both, so I'm posting it here (instead of opening a ticket).

    -- Felipe 

    1. Again, please use the issue tracker for RFEs and bugs. We can reassign tickets to the right plugin, but RFE left here will likely be simply forgotten.

  3. Unknown User (rmorrey)

    Is there a way to change the format of the information passed to Jira?  In particular, is there a way to remove the link to the Hudson build page?

  4. Unknown User (fred.hoare@redprairie.com)

    Does this plugin support and https connection to Jira?  I can't get it to display the links to Jira or make updates to the Jira issues.

  5. Unknown User (f.copperfield@gmail.com)

    The issue tracker is currently down, so I'll post my problem here. When the Jira issue key given in the commit comment does not exist (the committer made a typo, for example), the build fails. See exception below. In my view this information should be shown in the console output, but not cause the build to fail.

    Updating EXAMPLE-123
    FATAL: null
    AxisFault
     faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
     faultSubcode:
     faultString: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.
     faultActor:
     faultNode:
     faultDetail:
        {}com.atlassian.jira.rpc.exception.RemotePermissionException:null
        {http://xml.apache.org/axis/}hostname:example.jira.com
    
    com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104)
        at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90)
        at hudson.plugins.jira.soap.RemotePermissionException.getDeserializer(RemotePermissionException.java:75)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
        at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84)
        at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464)
        at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547)
        at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157)
        at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
        at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
        at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
        at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
        at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
        at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
        at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
        at org.apache.axis.client.Call.invoke(Call.java:2767)
        at org.apache.axis.client.Call.invoke(Call.java:2443)
        at org.apache.axis.client.Call.invoke(Call.java:2366)
        at org.apache.axis.client.Call.invoke(Call.java:1812)
        at hudson.plugins.jira.soap.JirasoapserviceV2SoapBindingStub.addComment(JirasoapserviceV2SoapBindingStub.java:3773)
        at hudson.plugins.jira.JiraSession.addComment(JiraSession.java:70)
        at hudson.plugins.jira.Updater.perform(Updater.java:84)
        at hudson.plugins.jira.JiraIssueUpdater.perform(JiraIssueUpdater.java:24)
        at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
        at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:480)
        at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:466)
        at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:454)
        at hudson.model.Build$RunnerImpl.post2(Build.java:145)
        at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:438)
        at hudson.model.Run.run(Run.java:1113)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
        at hudson.model.ResourceController.execute(ResourceController.java:93)
        at hudson.model.Executor.run(Executor.java:122)
    
  6. The Marvelution Jira Hudson integration looks very interesting. I haven't tried it yet, but one feature that it has solves a lot of complaints with this plugin, which is hudson polluting the comments. Especially with matrix builds. We had an issue with 2 (user) comments and 16 hudson commits. Noisy.

  7. Love the plugin so far!

    The one question I have is, if I checkin something to Subversion with my JIRA issue,
    the plugin correctly attaches that JIRA issues to my Hudson build console, just as
    you have explained.

    But if I stop my build for some reason, and retry my build, there is no longer a link
    between the JIRA issue and my Hudson build. It appears that the JIRA links in the
    Hudson build only show on the first time you build a Hudson revision. If I keep
    building that same Subversion revision, the JIRA link is only on the first build.

    Thanks for your help!

  8. When using a HTTPS Jira Url like this: https://18.4.45.13/jira

    The JIRA Plugin Config Section in Hudson always displays the warning: "java.security.cert.CertificateException: No subject alternative names present". Even though the self-signed certificate was imported into the correct keystore on the machine running Hudson.

    I've figured out that this might be the effect of using a self-signed certificate that lacks the "Subject Alternate Name" Extension. I've never seen this extension being in use for self-signed certificates so it would be nice if there would be an option in Hudson to suppress this error.

  9. Unknown User (patelp)

    How do i make it work with HTTPS Jira URL.

    If i enter http://example.jira.com it does not redirect to the https. My real URL is https://example.jira.com/secure/Dashboard.jspa

    If i enter the https URL then it says unable to connect.

    Any solution to this ?

  10. Unknown User (adama@atena.pl)

    Anyone tried to use this plugin with JIRA behind IIS proxy? I'm getting 401.2 Unauthorized when attemting to configure the plugin..

  11. I am trying to connect to a Jira over https but I continue to get the following error.

    sun.security.validator.ValidatorException: PKIX path building failed:
    sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

    In our case the Jira certificate is self signed. I found the following article that adds the certificate in order to trust it and have successfully followed the instructions and added the certificate to the store but I continue to get this error in the configuration dialog.

    http://blogs.sun.com/andreas/entry/no_more_unable_to_find

    Has anyone found a solution to this problem? Thanks in advance.

    1. Unknown User (stijn)

      I used to have the same problem; two things were causing this:
      1. server name was some.domain.com but I always used to enter the IP address directly; the certificate also used the IP. Changed the certificate to use the some.domain.com name
      2. make sure the certificate is imported into the correct keystore. I have both x86 and x64 versions, forgot to add it to both keystores, took me a while to figure that out.

      To import the certificates, I used Internet Explorer to get the cert and export it, then simply import using keytool:

      keytool -import -keystore JAVAHOME/lib/security/cacerts -file mycert.cer

  12. Unknown User (alank)

    Is there a way I can record my SVN revision number in Jira? We use it for build numbers of our products. It would be really nice if I could take this from a var I have defined or some other method.

  13. Unknown User (jhellwig)

    It seems as if the plugin does not support Jira 4.2! Is this correct?

    1. I just tested Jenkins 1.396 with Jira Plugin 1.27 using JIRA 4.2.2-b589, and it worked fine.

      Make sure that your JIRA user account has the correct setting / project access.

  14. Great work on an amazing plugin.

    Is there anyway to insert the SCM/Subverion user ID of the individual who committed a change into the JIRA comment?

  15. Unknown User (alank)

    I agree.  I would also like a way to pass an environment variable so I can pass my product version number.  The ability to enter these values in specific fields in Jira would be the next step.

  16. Very good plugin.

    Quick Question: How do you toggle the "Updated relevant Jira issues" check box from Jenkin's groovy Script Console for a particular job?

    Thanks!

  17. Great plugin. In order to provide more semantic data (query, output, report) it would be nice if the plugin could provide an "update field x with y" option. However, a set of updates.

    So, let's say: If I want to record the current build (for the feature "Fixed in Build") I would suggest something like "Update field 'Fixed in Build' with '$BUILD_NUMBER'". Or "Update field 'Fixed in Revision' with '$SVN_REVISION'". The more simple way would be a two-textfield-way (fieldname, fieldvalue). I think other scenarios like qa tagging  (after testing) are likely possible, too. Perhaps, in a later release, some fine tuning could control when a field should be updated (e.g. only update fixed in build if not set, only qa=3 if not under 1).

    If the plugin works again the official REST api by jira, the used user must be an administrator -- since jira 4.4 there is a bug denying field value changes if only a regular user tries to update a field's value

    Regards,

    Jan

  18. Great little plugin, I now have two way traceability between my build and bug tracking -- excellent

    One question: 

    For a Jenkins generated Jira comment, it contains the svn revision data plus the filename(s) that have been changed.  It would be nice to have that filename(s) linked so I can view that version of the file from svn.  As well a "diff" link to show the changes to the file.  Am I crazy for asking for just a bit more.  ;-)

    Do I need to configure Fisheye?   Right now I'm only running svn pserver, do I need http?  Do Jira and svn servers need to be colocated?

  19. Hi, I would like to use this plugin but I can't get it to access our JIRA. We can only access the JIRA server using a HTTP proxy.

    I've tried several ways to configure this, but none work:

    • Editing /etc/default/jenkins and add http.proxyHost & http.proxyPort to the JAVA_ARGS
    • Configuring via "Manage Jenkins" -> "Manage Plugins" -> tab "Advanced" (but seems that this has been changed  to only work for plugin updates; don't know the exact ticket)

    I keep getting the same error: The requested URL could not be retrieved.

    How can Jenkins access JIRA using a HTTP Proxy?
    Thanks,
    Joris

  20. Hi, 

    This is very useful plugin but it fills of the  comment section in Jira page, Any way just record the Jira ticket change and build number with hudson link, hide all the hudson recent changes log? Any update? It will be real pain once you merge many time same issue from different branches.

    praveen

  21. Hello,

    It will be great to have the possibility to connect to a Jira Server behind and HTTP-based Auth.
    I can't use Jira because our configuration is an HTTP-based Auth... So I must use Mantis, the Mantis plugin has this feature...

    For the 1.30 version ? ^^

    thanks!

    1. Hello,

      We also use HTTP-based Authentication for access to JIRA and would like to have this plugin supporting it. Current reply from JIRA server during configuration of plugin is: 401 Unauthorized

      Thanks and good luck!

  22. Hi,

    We use CLoudBees as forge and Jira hosted as issue tracker.

    Does this kind of configuration work or not ?

    What is the good url to use ? https://myproject.onjira.com/ or https://myproject.onjira.com/secure/ ?

    I jus try it and I got this stacktrace: FATAL: Could not initialize class org.apache.axis.wsdl.toJava.Utils
    java.lang.NoClassDefFoundError: Could not initialize class org.apache.axis.wsdl.toJava.Utils
    at org.apache.axis.encoding.TypeMappingImpl.finalGetDeserializer(TypeMappingImpl.java:482)
    at org.apache.axis.encoding.TypeMappingDelegate.getDeserializer(TypeMappingDelegate.java:114)
    at org.apache.axis.encoding.TypeMappingDelegate.getDeserializer(TypeMappingDelegate.java:111)
    at org.apache.axis.encoding.TypeMappingDelegate.getDeserializer(TypeMappingDelegate.java:111)
    at org.apache.axis.encoding.TypeMappingDelegate.getDeserializer(TypeMappingDelegate.java:102)
    at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:457)
    at org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:255)
    at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
    at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
    at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
    at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
    at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
    at org.apache.axis.client.Call.invoke(Call.java:2467)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at hudson.plugins.jira.soap.JirasoapserviceV2SoapBindingStub.getProjectsNoSchemes(JirasoapserviceV2SoapBindingStub.java:7965)
    at hudson.plugins.jira.JiraSession.getProjectKeys(JiraSession.java:62)
    at hudson.plugins.jira.JiraSite.getProjectKeys(JiraSite.java:201)
    at hudson.plugins.jira.JiraSite.existsIssue(JiraSite.java:255)
    at hudson.plugins.jira.JiraSession.existsIssue(JiraSession.java:175)
    at hudson.plugins.jira.Updater.getJiraIssues(Updater.java:164)
    at hudson.plugins.jira.Updater.perform(Updater.java:87)
    at hudson.plugins.jira.JiraIssueUpdater.perform(JiraIssueUpdater.java:29)
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
    at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:659)
    at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:857)
    at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:582)
    at hudson.model.Run.run(Run.java:1386)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:461)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:145)Best regards,

  23. What JIRA versions does this plugin support?

  24. For those ones getting the following exceptions while configuring Jira access in Jenkins, I solved it by adding the missing jars to Tomcat's lib folder.

    For the exception:

    java.lang.NoClassDefFoundError: Could not initialize class org.apache.axis.client.AxisClient

    Download Axis from here and copy the following jars to Tomcat's lib folder:

    • axis.jar
    • commons-discovery-0.2.jar
    • jaxrpc.jar
    • wsdl4j-1.5.1.jar

    For the exception:

    java.lang.NoClassDefFoundError: javax.mail.internet.MimeMultipart

    Download JavaMail from here and copy the following jars to Tomcat's lib folder:

    • mail.jar
  25. My JIRA instance is not available for browsing if user has not logged-in. JIRA plugin displays:

    Server returned HTTP response code: 503 for URL: http://jira.localnet.com/browse/
    

    Is it possible that JIRA plugin authenticates (e.g. via basic authentication, see JENKINS-2792) using the username/password provided at plugin configuration page? Alternatively JIRA plugin can query issues via RPC (/rpc/soap/jirasoapservice-v2?wsdl), then authentication would be easier.

  26. Hi,

    Is it possible to progress a JIRA issue in the workflow without using JQL? The reason is that we do not want to create a new intermediate state and ask the developers to update their issues before they do a commit. Rather we want to use Jenkins to grab the issue number and do the workflow action depending on the outcome of the build (put it into A if successful, B if not). I suppose this feature is somewhat already in the plugin, because it is possible to update the issue with a comment containing the result. Any help is appreciated.

    Thanks.

  27. Hi,

    Is it possible to add the Jenkins system config at the job level rather than in the global setting within hudson

    Thanks,

    Queenie

  28. The introductory material here seems to say that you can skip the username and password if you only want to hyperlink the changelog, not comment on issues. But in fact this does not seem to work. (JiraSite.createSession simply returns null if there is no authentication.)

  29. Hi, i have a problem, when I enter the url "https://user.atlassian.net/secure/Dashboard.jspa", I recieve the next message "https://user.atlassian.net/secure/rpc/soap/jirasoapservice-v2?wsdl" in red , and if I apply the changes i recieve the message "Unable to connect https://user.atlassian.net/secure/Dashboard.jspa/" and i don now which is te error

  30. I can see some changes pushed after JIRA plugin 1.37 by Kutzi to resolve the slow performance of Jenkins changelog when this plugin is switched on ("JENKINS-18155: cache recently accessed JIRA issues") which we would like to put into our environment, before I explore that option (which opens up a whole heap of questions on 'How?'), is there an ETA for when 1.38 will be available to the general user community including this fix?  Thanks!

  31. We have one jenkins job per branch of a project, and multiple open versions in Jira. If we make a change in one branch, we merge the change up the open branches. Sometimes (often) developers forget to update the ticket with the correct 'Fixed in' for each branch that they merge to.

    I would love it if a jenkins job pulls in changes for a ticket that it is able to update the 'Fixed in' for that ticket to a version for this jenkins job.

    It looks like the build parameters might do the job, except our jenkins kicks off a build whenever a change happens on the branch for that build. So the build parameter wouldn't be filled in.

    Can someone help me with what I think should be a common workflow? I'm sure this plugin addresses my needs, I'm just not sure how.

    Thanks!

  32. We have setup a workflow action in JIRA that marks issues with a "Deployed" status so our QA team knows which issues are ready to test.

    What is the best way to update the issues through Jenkins-JIRA integration? I see that you can use the execute workflow action, but that doesn't allow us to do this on a per issue basis. You have to specify JQL to get a list of issues. The contextual help for the JQL says that you can use

      issue = $ISSUE_ID

    but that causes an error which fails the promotion. I also tried

      issue = "$ISSUE_ID"

    but that failed as well.

    Our promotions don't happen on every build, but we would like to have all issues that appear in the commit log since the last promotion to be updated using this workflow action.

    1. Hello Brad,

      Did you get this resolved. I ran into the same issue.

  33. Hello,

    It seems that Jenkins JIRA plugin does NOT honor "http.nonProxyHosts" passed to Jenkins with -D via JENKINS_JAVA_OPTIONS (in /etc/sysconfig/jenkins).

    Instead, you have to use "No Proxy Host" under Manage Plugins -> Advanved to exclude a JIRA server from being accessed via proxy.

    Could somebody confirm this? Is this a bug?

    I would expect that "http.nonProxyHosts" applies to the whole Jenkins instance including plugins.

    PS. I noticed that a similar issue has been raised by another user for Jenkins SVN plugin (see https://issues.jenkins-ci.org/browse/JENKINS-17448).

    Thanks,

    Ioannis

  34. Is it possible to use this plugin to update a Jira from Resolved to Needs Verification?

    I use it to update Jira, which puts comments in the Jiras that were identified by a regex in SCM commit messages. I'd like to update the status of those Jiras as well.

    I was trying the Jira Issue Updater plugin but saw it may have been deprecated by this plugin.

    1. Hi,

      we need this feature too?

      Any plans when it implemented?

      Thanks!

  35. What are the 'Atlassian Confluence Open Source Project License' terms?

    Are we allowed to make changes to the plugin and use it in a commercial environment?

  36. This works great.  simple to setup.

    I confused about what the post-build "update relevant JIRA issues" does.  I can update the issues with a new build event, but this one doesn't appear to update anything. 

  37. Is this plugin works for Jira 6.0.8 ?

    Please advise.

    -Shivendra

  38. Does anyone know if work is being done for https://issues.jenkins-ci.org/browse/JENKINS-18166 on the REST API?  We don't intend to enable the RPC (SOAP) option because it is in a deprecated state.  -Thank-You-

  39. I’ve started using your JIRA Plugin for Jenkins, and out of the box it works great for solving my initial problem of documenting which Jenkins build JIRA changes went into.

    However I am now looking at the next step to work out how I can more fully integrate Jenkins and JIRA. 

    Is there a guide about how to use your plugin for Jenkins / JIRA integration should occur:

    e.g.

    • when to create the build
    • When to generate release notes
    • When to mark JIRA version as released
    • Move issues matching JQL to the specified version

    Also, are you aware of whether this functionality is also supported by the Marvelution / Atlassian supported JIRA / Jenkins plugins?

    If I have to migrate should I do it now or later?

  40. I'm trying to setup this plugin on our in-house Jenkins system to communicate with our Jira OnDemand instance.  However, I cannot get the plugin to authenticate successfully with the Jira instance.  I've followed all the steps listed above, but I still cannot get it to authenticate.

    Has anyone been able to get the plugin working with an OnDemand instance?

  41. is it possible to use jira plugin in a job which executes only build without git clone.

    git clone/checkout is executed in other job.

  42. Hello.

    I want Jenkins instead of adding comment update specific text field "Fixed in Build". 

    This is different to Release! Release has many many builds until it is released.

    Could you please implement such feature? Selecting field name + selecting pattern for what to put there.

  43. For a build:

    1. is there a way to apply the workflow action on the issues that participated in the build only ?
    2. is there also a way to define different workflow action depending on the success (or failure) of the build ?

    Thanks

  44. Does this plugin still work for anyone? I'm on Jenkins ver. 1.609.1 and Jira 6.4.5. 

  45. JIRA Cloud is going to be ending support for the SOAP API on July 6, 2015, and it seems like this plugin uses it.

    Will this plugin be migrating to use REST APIs instead?

    Atlassian has given this guide: https://developer.atlassian.com/jiradev/api-reference/jira-api-status/jira-rpc-services/jira-soap-to-rest-migration-guide?utm_source=alert-email&utm_medium=email&utm_campaign=jirasoap

    Thanks for the great plugin!

    Hubert

  46. Dear Plugin Devs,

    Is it possible to write more info about how to use "Environment Variables" when specifying a path to store Release Notes? Also, in case of this field is empty, there must be some default value for this. Up to now, I am not able to see generated documents (based on the provided How To), not a word in the Terminal logs.

  47. 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.

    This gives the reason for the plugin code migration but what is the minimal JIRA version introducing the REST API for which the plugin claims/targets compliance with?

    Upgrading to 2.2 and using JIRA 6.3.14, I got the two following regressions:

    The plugin still succeeds in writing comments on JIRA (despite JENKINS-33551) but the second issue (JENKINS-33552) looks like an API incompatibility.

  48. Hi,

    I am getting the below error when Jenkins is trying to update issues in JIRA:

    JIRA Update Build Step

    -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -

    Unable to parse JSON result: {

    "expand": "names,schema",

    "startAt": 0,

    "maxResults": 1000,

    "total": 1,

    "issues": [{

    "expand": "operations,versionedRepresentations,editmeta,changelog,transitions,renderedFields",

    "id": "289777",

    "self": "https://url/rest/api/2/issue/11111",

    "key": "TE-ABCDE",

    "fields": {

    "summary": "A summary.",

    "versions": [{

    "self": "https://url/rest/api/2/issue/11111",

    "id": "11111",

    "description": "Rel 5.0",

    "name": "Rel 5.0",

    "archived": false,

    "released": true,

    "releaseDate": "2015-08-03"

    }]

    }

    }]

    }

    com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "releaseDate" (class info.bluefloyd.jira.model.VersionSummary), not marked as ignorable(6 known properties: "archived", "id", "description", "released", "name", "self"])

    at[Source: {

    "expand": "names,schema",

    "startAt": 0,

    "maxResults": 1000,

    "total": 1,

    "issues": [{

    "expand": "operations,versionedRepresentations,editmeta,changelog,transitions,renderedFields",

    "id": "11111",

    "self": "url/rest/api/2/issue/11111",

    "key": "TE-ABCDE",

    "fields": {

    "summary": "Summary",

    "versions": [{

    "self": "url/rest/api/2/version/11111",

    "id": "11111",

    "description": "Rel 5.0",

    "name": "Rel 5.0",

    "archived": false,

    "released": true,

    "releaseDate": "2015-08-03"

    }]

    }

    }]

    }; line: 1, column: 603](through reference chain: info.bluefloyd.jira.model.IssueSummaryList["issues"] - > java.util.ArrayList[0] - > info.bluefloyd.jira.model.IssueSummary["fields"] - > info.bluefloyd.jira.model.FieldSummary["versions"] - > java.util.ArrayList[0] - > info.bluefloyd.jira.model.VersionSummary["releaseDate"])

    Seems like there is an issue with the releaseDate attribute in the Affects Version field of JIRA
    Kindly suggest a solution.

  49. Is it at all possible to update Jira issues with this plug in, for example to set a Jira issue to closed or resolved if a Jenkins project build is successful?

  50. I am using Jenkins version 1.635 with promotion plugin 2.27.  Whenever I use the jira plugin in the promotion block (to create new version, or set a jira release version) the promotion fails and the jira action fails.  Outside of the promotion block the jira action is successful (ie. as a post build step).

    The jira plugin version I am using is 2.0.3.

    Has anyone else run into this issue?

    FATAL: Unable to add version RELNOTE-6.0.0 to jira project RELNOTE
    java.lang.NullPointerException
    at hudson.plugins.jira.JiraVersionCreator.perform(JiraVersionCreator.java:77)
    at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:344)
    at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:286)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
    at hudson.model.Run.execute(Run.java:1741)
    at hudson.model.Run.run(Run.java:1679)
    at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:231)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)
    Finished: FAILURE

  51. Hi,

    I have set up the 2.2.1 version of this plugin with my jenkins instance. I am having issue with "Create jira issue" upon job failure. The update relevant  jira issue part is working fine. 

    Below is the error that i am getting ERROR: Build step failed with exception
    java.lang.NullPointerException
    at hudson.plugins.jira.JiraCreateIssueNotifier.getStatus(JiraCreateIssueNotifier.java:186)
    at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:332)
    at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:133)
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)
    at hudson.model.Build$BuildExecution.post2(Build.java:185)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)
    at hudson.model.Run.execute(Run.java:1766)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:408)
    Build step 'Create Jira Issue' marked build as failure
    Need help fixing it.

  52. Is there any documentation available which details how the "Generate Release Notes" option works please?  I'm struggling to set up a test and want to understand more before I invest more time trying to get it working.

    Specifically I am interested to find out:

    • what data is extracted (e.g. can specific fields within JIRA be specified for extraction?)
    • what format do the Release Notes take: ~.txt, PDF? In the example given it suggests only that you can echo $JiraReleaseNotes. I'd like to know what to expect in that variable.
    • why is an Issue Filter necessary? I would expect that the list of JIRA cases included in the Release Notes to be the cases that were included in the build or have I got that wrong?

    I might just add that at this stage I do not want to "Mark a JIRA version as Released", nor do I want to have the plugin update the status of the affected JIRA cases. I'm just looking for a way to automate the Release Notes.

  53. OK

    I have one question regarding this plugin. I am using local git repository which is accessible via http (apache web server). I am able to configure that in Jenkins and am successfully able to perform builds (maven builds). I downloaded this jira plugin and am able to connect to jira. What I am not able to do is associate my builds directly with the jira issues using the default issue selector option selected for the built. NOTE: In my gloabl Jenkins configuration I have the Issue Pattern empty. I was expecting Jenkins to be able to parse my "git commit comments" and do the association automatically. That is not happening. Can someone help me with this.

    The documentation on this topic is difficult to find.

    NOTE: the association works if I use JQL(Jira QL) but I was trying to use the git commit comments that have Jira ID to achieve the same.

    1. OK

      I just solved my own issue; just for everyone's benefit. It was a silly mistake; I did not commit the changes into git repository so the comments with Jira Issue ID were not available for this awesome plugin to look at and parse the git commit text, once I committed the same the plugin correctly updated the Jira issue comments.

  54. Hi,

    Is there anyway to use BUILD_DISPLAY_NAME instead of using #BUILD_NUMBER in the JIRA comment? something like:

    SUCCESS: Integrated in  xxxxxxx #275

    to 

    SUCCESS: Integrated in  xxxxxxx #1.0.0.121

    ?

  55. Hey,
    is it possible to set the global JIRA plugin configuration via groovy script?

    Much appreciated.
    Thx

  56. I'm receiving an escaped HTML issue in Jenkins ver. 2.73.2 with version 2.4.2 of this plugin. Please advise. Thanks!

    1. Please let me know if you get the fix. I am also facing the similar issue

  57. Hi,

    I am not able to see JIRA issue key links on Jenkins changelog page. Please let me know how to fix this.

  58. Hi guys,

    do you know how to put an entry in CI Build Panel every time my build is finished successfully. To insert an entry in "comment" panel I can use jiraissuecomment but for CI Build Panel I've no idea at the moment.

    Can you help me concerning this ? Thanks

     

    1. I'm guessing that you're referring to CI Builds panel provided by Marvelution JIRA plugin - https://docs.marvelution.org/display/JJI/CI+Build+Panels. I believe the entries there are automatically linked by the JIRA ticket ID when Jenkins is linked with JIRA with this plugin. Check https://docs.marvelution.org/display/JJI/Jenkins+Configuration+in+JIRA and you might want to ask Marvelution for support around it.

  59. Do not use JIRA Plugin 2.4.2 version with Jenkins CloudBees Jenkins Enterprise 2.89.1.7-rolling

    or Jenkins Community version 2.89.2.

    It will eat up ~ 200 files handle in 0.5 hours.

    1. Can you file a bug report with more details?

  60. Hi all, is there any way/are there any plans to enable signing in to Jira with SSO using this plug in? My organization would like to make our Jira instance SSO only, but don't want to break this workflow. 

  61. Hello Everyone,

    I am facing one basic issue I am getting started with Jenkins & JIRA integration and I need to use Basic authorization token instead of username and password, where this plug only allows me to enter user and password. when I tried with null user empty I get 401 not authorized error.

     

    Is there anyway where I can use basic authorization token and hit this JIRA Rest API server from this jenkins JIRA issue updater operation. 

     

    I am using latest plugins available.

     

    Thanks in advance.

  62. Hi all, 

    I'm trying to create a jenkins container with some preconfigured functionalities and plugins. One of them is to provide automatically the integration with a JIRA using this plugin. 

    What I'm doing is to run a clean jenkins container, install JIRA plugin, configure the connection with JIRA succesfully, check and get the files created and modified in the container (i.e., hudson.plugins.jira.JiraProjectProperty.xml, where jira's username & pwd is configured) and put them on my custom jenkins image using copy in the dockerfile. 

    When I run my Jenkins image, I can see that the integration has been created in the Management section, with the right URL, User and a password informed, but if I click the "validate" button it fails. If I retype the password again and validate, it works. 

    I've seen that password in JiraProjectProperty.xml is encripted, so I suppose there's something that doesn't allow same configuration to work on different containers. I've checked all the Jenkins home folder to check with files changed, and tried to also copy in the container the Identity.key.enc and scriptApproval.xml files, but still not working. Same behaviour. 

    Any idea about how to do that? Or maybe I'm trying to do something impossible? 

     

    Thxs! 

     

  63. Hi All

     

    I am working on updating the Release Versions for issues that are part of the current build. I am trying to use the "Move issues matching jql to specified version" plugin. I am setting the new version to be updated and I have checked the "Add Target Release" and the jql is "issue in (${JIRA_ISSUES})" The problem I am seeing is that this plugin is not getting called at all. There are no errors or logs mentioning anything from this plugin.

    Before this plugin I can creating a new JIRA version using the Create version plugin and that works fine.

     

    Any idea why this is not working? I am on version 3.0.0 of the plugin.

     

    Thanks

    Tejas

    1. I believe this is related to this issue already raised?

       

      JENKINS-50553 - Getting issue details... STATUS

       

      Regards

      Tejas

  64. Hi,

     

    I am not able to access the ENV variable in `Post-build Action`, but it gives error.

     

    WARNING: jira rest client get issue from jql search error. cause: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={}, errorMessages=[The issue key '$MY_ISSUE_ID' for field 'issue' is invalid.]}]}
        java.util.concurrent.ExecutionException: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={}, errorMessages=[The issue key '$MY_ISSUE_ID' for field 'issue' is invalid.]}]}
        	at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)
        	at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:262)
        	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
        	at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
        	at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:107)
        	at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:177)
        	at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)
        	at hudson.plugins.jira.selector.JqlIssueSelector.findIssueIds(JqlIssueSelector.java:49)
        	at hudson.plugins.jira.Updater.perform(Updater.java:85)
        	at hudson.plugins.jira.JiraIssueUpdater.perform(JiraIssueUpdater.java:64)
        	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
        	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
        	at hudson.model.Build$BuildExecution.post2(Build.java:186)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
        	at hudson.model.Run.execute(Run.java:1749)
        	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
        	at hudson.model.ResourceController.execute(ResourceController.java:97)
        	at hudson.model.Executor.run(Executor.java:421)
        Caused by: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={}, errorMessages=[The issue key '$MY_ISSUE_ID' for field 'issue' is invalid.]}]}
        	at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:176)
        	at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:170)
        	at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:67)
        	at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:11)
        	at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:268)
        	at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:158)
        	at com.google.common.util.concurrent.Futures$6.run(Futures.java:975)
        	at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
        	at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149)
        	at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134)
        	at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170)
        	at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
        	at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:268)
        	at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:158)
        	at com.google.common.util.concurrent.Futures$6.run(Futures.java:975)
        	at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
        	at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149)
        	at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134)
        	at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170)
        	at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
        	at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$1$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:46)
        	at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:197)
        	at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.runInContext(SettableFuturePromiseHttpPromiseAsyncClient.java:90)
        	at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.run(SettableFuturePromiseHttpPromiseAsyncClient.java:192)
        	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        	at java.lang.Thread.run(Thread.java:748)

    Detail error explain in stackoverflow.

  65. We have following problem with the connection timeout parameter. We can change the parameter in the Jenkins-UI or in hudson.plugins.jira.JiraProjectProperty.xml, but after every restart of Jenkins it is set back in the UI to the default = 10.
    Value in the xml stays correct until we save the configuration over UI.
    Jenkins 2.138.1  Jira-Plugin 3.0.1 (also 3.0.2)
    There are no additional informations in the log.

  66. The plug-in has a post-build step to "update relevant issues". What is the alternative to this for pipeline jobs (which do not support post-build steps)?

    1. Based on what I read on the Pipeline compatibility page, I can answer my own question. In a declarative pipeline, it suffices to add this:

      post {
      	success {
      		step([$class: 'hudson.plugins.jira.JiraIssueUpdater', 
      			issueSelector: [$class: 'hudson.plugins.jira.selector.DefaultIssueSelector'], 
      			scm: scm])
      	}
      }
  67. Builds have been failing since the release of 3.0.3 - have had to revert back to 3.0.2:

    • 3.0.3 Error:
      • [JIRA] Updating issues using workflow action Ready for QA.
        [JIRA] JQL: project in (VA) and status in ("Code Merged to Branch") and sprint is not Empty and fixVersion is not Empty
        ERROR: Build step failed with exception
        java.lang.IllegalArgumentException
        	at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1314)
        	at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1237)
        	at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
        	at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457)
        	at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426)
        	at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:942)
        	at hudson.plugins.jira.JiraIssueUpdateBuilder.perform(JiraIssueUpdateBuilder.java:105)
        	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
        	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
        	at hudson.model.Build$BuildExecution.build(Build.java:206)
        	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
        	at hudson.model.Run.execute(Run.java:1815)
        	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
        	at hudson.model.ResourceController.execute(ResourceController.java:97)
        	at hudson.model.Executor.run(Executor.java:429)
        Build step 'JIRA: Progress issues by workflow action' marked build as failure
    • 3.0.4 Error: 
      • [JIRA] Updating issues using workflow action Ready for QA.
        [JIRA] JQL: project in (VA) and status in ("Code Merged to Branch") and sprint is not Empty and fixVersion is not Empty
        [JIRA] An error occurred while progressing issues:
        java.util.concurrent.TimeoutException: Timeout waiting for task.
        	at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)
        	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
        	at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
        	at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)
        	at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194)
        	at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:135)
        	at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:956)
        	at hudson.plugins.jira.JiraIssueUpdateBuilder.perform(JiraIssueUpdateBuilder.java:105)
        	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
        	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
        	at hudson.model.Build$BuildExecution.build(Build.java:206)
        	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
        	at hudson.model.Run.execute(Run.java:1815)
        	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
        	at hudson.model.ResourceController.execute(ResourceController.java:97)
        	at hudson.model.Executor.run(Executor.java:429)
        Build step 'JIRA: Progress issues by workflow action' changed build result to FAILURE

    Reverting back to 3.0.2 and the Build completes successfully without issue. Any ideas? What additional information would you need to troubleshoot?

    Thanks

    -Josh Brozen

  68. Hi All,

    I have use case that I have to create Jira ticket for other teams after completion of Jenkins Job. I have support intake page of different teams in which we need to provide some information and Jira task can be created for them, can anyone guide about how it is possible to achieve it using jenkins Jira plugin?

     Suggestions are also appreciated.


    Thanks,

    Shobhit