Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61175

Provide different JiraIssueUpdater for cloud and server

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Component/s: jira-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      According to Ben_Kelley from ATLASSIAN TEAM the currently used library

      jira-rest-java-client is for server-edition of Jira only,

      see https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944

      Ben_Kelley ATLASSIAN TEAM Tuesday
      Please note the section under "Compatibility with Jira" for JRJC on https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview

      The Jira REST Java Client works with Jira Server, but not with Jira Cloud.

       

      When communicating with the cloud edition a self-generated (java) client should be used:

      https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133

       

      As the jenkins jira-plugin should work with cloud edition and onpremise server edition of Jira I guess there should be
      a "generic api" 
      above of the https://bitbucket.org/atlassian/jira-rest-java-client 
      and the self-generated

      encapsulating the core-jira-functions necessary for jira-plugin

      to be sure all functions provided by jira-plugin work on both.

       

      Current APIs:

      Server Platform:

      https://docs.atlassian.com/software/jira/docs/api/REST/8.7.1/

      Cloud Platform: (v3 is already available as beta)

      https://developer.atlassian.com/cloud/jira/platform/rest/v2/

       

        Attachments

          Issue Links

            Activity

            sc_rsc Stefan Cordes created issue -
            sc_rsc Stefan Cordes made changes -
            Field Original Value New Value
            Link This issue relates to JENKINS-57500 [ JENKINS-57500 ]
            sc_rsc Stefan Cordes made changes -
            Link This issue relates to JENKINS-53794 [ JENKINS-53794 ]
            sc_rsc Stefan Cordes made changes -
            Description According to Ben_Kelley from ATLASSIAN TEAM the currently used library

            jira-rest-java-client is for server-edition of Jira only,

            see [https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944]
            {quote}
            Ben_Kelley ATLASSIAN TEAM Tuesday
            Please note the section under "Compatibility with Jira" for JRJC on https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview

            The Jira REST Java Client works with Jira Server, but not with Jira Cloud.
            {quote}
             

            When communicating with the cloud edition a self-generated (java) client should be used:

            [https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133]

             

            As the jenkins jira-plugin should work with cloud edition +and+ onpremise server edition of Jira I guess there should be
            a "generic api" 
            above of the [https://bitbucket.org/atlassian/jira-rest-java-client
            and the self-generated

            encapsulating the core-jira-functions necessary for jira-plugin

            to be sure all functions provided by jira-plugin work on both.

             

             
            According to Ben_Kelley from ATLASSIAN TEAM the currently used library

            jira-rest-java-client is for server-edition of Jira only,

            see [https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944]
            {quote}Ben_Kelley ATLASSIAN TEAM Tuesday
             Please note the section under "Compatibility with Jira" for JRJC on [https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview]

            The Jira REST Java Client works with Jira Server, but not with Jira Cloud.
            {quote}
             

            When communicating with the cloud edition a self-generated (java) client should be used:

            [https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133]

             

            As the jenkins jira-plugin should work with cloud edition +and+ onpremise server edition of Jira I guess there should be
             a "generic api" 
             above of the [https://bitbucket.org/atlassian/jira-rest-java-client
             and the self-generated

            encapsulating the core-jira-functions necessary for jira-plugin

            to be sure all functions provided by jira-plugin work on both.

             

            Current APIs:

            Server Platform:

            https://docs.atlassian.com/software/jira/docs/api/REST/8.7.1/

            Cloud Platform: (v3 is already available as beta)

            https://developer.atlassian.com/cloud/jira/platform/rest/v2/

             
            Hide
            warden Radek Antoniuk added a comment -

            It would be great to have genericness in the plugin but as you see there is not enough community engagement for anyone to develop this.

            Additionally Atlassian created a new plugin targeted for the cloud version: https://plugins.jenkins.io/atlassian-jira-software-cloud/

            Show
            warden Radek Antoniuk added a comment - It would be great to have genericness in the plugin but as you see there is not enough community engagement for anyone to develop this. Additionally Atlassian created a new plugin targeted for the cloud version: https://plugins.jenkins.io/atlassian-jira-software-cloud/
            warden Radek Antoniuk made changes -
            Resolution Won't Fix [ 2 ]
            Status Open [ 1 ] Closed [ 6 ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              sc_rsc Stefan Cordes
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: