Pivotal Tracker has retired v3 of REST API - integration with v5 is required

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Low
    • None
    • Affects Version/s: 7.6.7
    • Component/s: Jira Importers Plugin
    • None
    • 7.06
    • 1
    • Severity 2 - Major
    • 1

      Pivotal Tracker integration does not work due to Pivotal retiring v3 of REST API

      Expected Results

      At the moment Pivotal only offers v5 of REST API.

      Actual Results

      Jira Pivotal Client plugin is hardcoded to use v3 of REST API.

      The below exception is thrown in the xxxxxxx.log file:

      2019-01-31 04:50:25,129 http-nio-8443-exec-19 INFO cmcej 290x221486x1 v31xb0 10.90.46.167,10.64.131.35 /secure/admin/PivotalSetupPage.jspa [c.a.j.p.i.imports.pivotal.PivotalImporterController] Cannot login to Pivotal Tracker site
      com.atlassian.jira.plugins.importer.imports.pivotal.PivotalHttpException: HTTP Error code HTTP/1.1 404 Not Found returned by Pivotal Tracker
      	at com.atlassian.jira.plugins.importer.imports.pivotal.PivotalClient.openGet(PivotalClient.java:155)
      	at com.atlassian.jira.plugins.importer.imports.pivotal.PivotalClient.login(PivotalClient.java:105)
      	at com.atlassian.jira.plugins.importer.imports.pivotal.PivotalImporterController.validateRemoteSiteConnection(PivotalImporterController.java:107)
      	at com.atlassian.jira.plugins.importer.imports.pivotal.PivotalImporterController.createImportProcessBean(PivotalImporterController.java:59)
      	at com.atlassian.jira.plugins.importer.imports.pivotal.web.PivotalSetupPage.doExecute(PivotalSetupPage.java:67)
      	... 1 filtered
      	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)
      	at com.atlassian.jira.plugins.importer.web.ImporterProcessSupport.execute(ImporterProcessSupport.java:152)
      	... 7 filtered
      	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
      	... 48 filtered
      	at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:62)
      	... 12 filtered
      	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
      	... 62 filtered
      	at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
      	... 1 filtered
      	at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
      	... 39 filtered
      	at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
      	... 10 filtered
      	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
      	... 4 filtered
      	at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
      	... 26 filtered
      	at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
      	... 23 filtered
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
      	at java.lang.Thread.run(Thread.java:745)
      

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            Assignee:
            Unassigned
            Reporter:
            Andrey Patyuchenko (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: