JIRA Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID jira Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.39
Oct 06, 2013
1.533
maven-plugin (version:1.533)
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Olivier Lamy (id: olamy)
Usage Installations 2013-Jun 5296
2013-Jul 5567
2013-Aug 5574
2013-Sep 5632
2013-Oct 5841
2013-Nov 5741
2013-Dec 5678
2014-Jan 6139
2014-Feb 6310
2014-Mar 6529
2014-Apr 6624
2014-May 6686

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. 

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

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.

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.

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.

Related Resources

  • Check also the Marvelution Jira Hudson Integration which provides a two-way solution Hudson->JIRA and JIRA->Hudson

History

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 issue #13998
Version 1.33 (Jun 1, 2012)
  • Support workflow steps as build actions and/or post-build notifiers issue #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)
  • issue #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 (issue #1703)
Version 1.12
  • A typo in the commit message shouldn't break builds (issue #1593)
  • Postpone JIRA updates until a successful build is obtained (issue #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 (issue #828)
Version 1.6
  • Relaxed the JIRA project key regexp a little bit to allow numbers (issue #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 issue #694

Labels

plugin-maven plugin-maven Delete
plugin-external plugin-external Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Aug 08, 2007

    Peter Schuebl says:

    It would be great if the pattern for the JIRA project key would be configurable ...

    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. Aug 08, 2007

      Kohsuke Kawaguchi says:

      Please use the issue tracker for RFEs and bugs.

      Please use the issue tracker for RFEs and bugs.

      1. Sep 02, 2007

        Kohsuke Kawaguchi says:

        Implemented in 1.6.

        Implemented in 1.6.

  2. Feb 28, 2008

    felipeal - says:

    Kohsuke,  It would be nice if the Hudson Jira and Perforce plugins are int...

    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. Feb 29, 2008

      Kohsuke Kawaguchi says:

      Again, please use the issue tracker for RFEs and bugs. We can reassign tickets t...

      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. Sep 15, 2008

    Rex Morrey says:

    Is there a way to change the format of the information passed to Jira?  In ...

    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. Nov 05, 2008

    Fred Hoare says:

    Does this plugin support and https connection to Jira?  I can't get it to d...

    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. Aug 18, 2009

    Frank says:

    The issue tracker is currently down, so I'll post my problem here. When the Jira...

    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. Aug 20, 2009

    jlongman - says:

    The Marvelution Jira Hudson integration looks very interesting. I haven't trie...

    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. Jan 22, 2010

    Jay Blanton says:

    Love the plugin so far! The one question I have is, if I checkin something to S...

    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. Apr 29, 2010

    Oliver Walsh says:

    When using a HTTPS Jira Url like this: https://18.4.45.13/jira The JIRA Plugin ...

    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. Jun 30, 2010

    pritesh patel says:

    How do i make it work with HTTPS Jira URL. If i enter http://example.jira.com i...

    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. Jul 02, 2010

    Adam A says:

    Anyone tried to use this plugin with JIRA behind IIS proxy? I'm getting 401.2 Un...

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

  11. Jul 21, 2010

    nporter - says:

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

    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. Dec 14, 2010

      stijn says:

      I used to have the same problem; two things were causing this: 1. server name wa...

      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. Aug 26, 2010

    Alan K says:

    Is there a way I can record my SVN revision number in Jira? We use it for build...

    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. Jan 03, 2011

    Juergen Hellwig says:

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

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

    1. Mar 02, 2011

      Cliffano Subagio says:

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

      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. Feb 02, 2011

    Ricardo Gladwell says:

    Great work on an amazing plugin. Is there anyway to insert the SCM/Subverion u...

    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. Feb 02, 2011

    Alan K says:

    I agree.  I would also like a way to pass an environment variable so I can ...

    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. May 10, 2011

    Alex Gray says:

    Very good plugin. Quick Question: How do you toggle the "Updated relevant Jira ...

    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. Sep 21, 2011

    knalli - says:

    Great plugin. In order to provide more semantic data (query, output, report) it ...

    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. Sep 29, 2011

    Brent Webster says:

    Great little plugin, I now have two way traceability between my build and bug tr...

    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. Oct 04, 2011

    Joris Lambrechts says:

    Hi, I would like to use this plugin but I can't get it to access our JIRA. ...

    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. Oct 07, 2011

    PRAVEEN MARAKKOOR says:

    Hi,  This is very useful plugin but it fills of the  comment section ...

    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. Oct 30, 2011

    Nicolas Griffet says:

    Hello, It will be great to have the possibility to connect to a Jira Server beh...

    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. Mar 08, 2012

      Peter Kolínek says:

      Hello, We also use HTTP-based Authentication for access to JIRA and would like ...

      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. Nov 02, 2011

    Cyril Lakech says:

    Hi, We use CLoudBees as forge and Jira hosted as issue tracker. Does this kind...

    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. Jan 06, 2012

    Darren Osten says:

    What JIRA versions does this plugin support?

    What JIRA versions does this plugin support?

  24. Jan 08, 2012

    Ariel Kogan says:

    For those ones getting the following exceptions while configuring Jira access in...

    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. May 11, 2012

    dma_k - says:

    My JIRA instance is not available for browsing if user has not logged-in. JIRA p...

    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. Nov 30, 2012

    Marcell Jusztin says:

    Hi, Is it possible to progress a JIRA issue in the workflow without using JQL? ...

    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. Feb 12, 2013

    Queenie Chow says:

    Hi, Is it possible to add the Jenkins system config at the job level rather tha...

    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. Mar 07, 2013

    Jesse Glick says:

    The introductory material here seems to say that you can skip the username and p...

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

    1. Apr 03, 2013

      John Gibson says:

      Unfortunately this is a long-standing issue: https://issues.jenkins-ci.org/brows...

      Unfortunately this is a long-standing issue: https://issues.jenkins-ci.org/browse/JENKINS-1904.

  29. May 09, 2013

    Jonathan Sanchez says:

    Hi, i have a problem, when I enter the url "https://user.atlassian.net/secure/Da...

    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. Aug 06, 2013

    John Speak says:

    I can see some changes pushed after JIRA plugin 1.37 by Kutzi to resolve the slo...

    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. Aug 14, 2013

    scooper4711 Cooper says:

    We have one jenkins job per branch of a project, and multiple open versions in J...

    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. Aug 21, 2013

    Brad Curfman says:

    We have setup a workflow action in JIRA that marks issues with a "Deployed" stat...

    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.

  33. Aug 29, 2013

    gecon27 - says:

    Hello, It seems that Jenkins JIRA plugin does NOT honor "http.nonProxyHost...

    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. Sep 20, 2013

    Mike Harris says:

    Is it possible to use this plugin to update a Jira from Resolved to Needs Verifi...

    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. Jan 31

      Lalso S. says:

      Hi, we need this feature too? Any plans when it implemented? Thanks!

      Hi,

      we need this feature too?

      Any plans when it implemented?

      Thanks!

  35. Oct 25, 2013

    Alina Danila says:

    What are the 'Atlassian Confluence Open Source Project License' terms? Are we a...

    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. Dec 11, 2013

    Jason Little says:

    This works great.  simple to setup. I confused about what the post-build "...

    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. Mar 07

    Shivendra Dwivedi says:

    Is this plugin works for Jira 6.0.8 ? Please advise. -Shivendra

    Is this plugin works for Jira 6.0.8 ?

    Please advise.

    -Shivendra

  38. Mar 13

    Walter Kacynski says:

    Does anyone know if work is being done for https://issues.jenkins-ci.org/browse/...

    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. May 06

    Donald Jones says:

    I’ve started using your JIRA Plugin for Jenkins, and out of the box it works gre...

    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?