• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • jira-plugin
    • None

        [JENKINS-56987] Atlassian Jira API Changes for GDPR

        Olivier Lamy created issue -
        Olivier Lamy made changes -
        Summary Original: Jira Atlassian API Changes for GDPR New: Atlassian Jira API Changes for GDPR

        Robert Fults added a comment -

        SOAP API is deprecated as of 4/14/2019: https://blog.developer.atlassian.com/app-opt-in-api-migration/

        This has caused the Confluence Publisher plugin to begin failing, not sure what other plugins are broken at this time.  Issue was identified by Atlassian support under issue PSCLOUD-23492.

        Robert Fults added a comment - SOAP API is deprecated as of 4/14/2019:  https://blog.developer.atlassian.com/app-opt-in-api-migration/ This has caused the Confluence Publisher plugin to begin failing, not sure what other plugins are broken at this time.  Issue was identified by Atlassian support under issue PSCLOUD-23492.
        benoit guerin made changes -
        Link New: This issue relates to JENKINS-60305 [ JENKINS-60305 ]
        Olivier Lamy made changes -
        Assignee New: Olivier Lamy [ olamy ]
        Resolution New: Fixed [ 1 ]
        Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]

        The removal of the name attribute seems to be causing jql to now fail using plugin 3.0.12

         

        I can see the following line here which looks to be trying to still get it. Looks like the plugin needs to use a later version of the rest client. It currently uses 5.0.4 but the latest available is 5.1.6

        https://docs.atlassian.com/jira-rest-java-client-parent/5.0.4/xref/com/atlassian/jira/rest/client/internal/json/JsonParseUtil.html#L192

         

        Line causing issue

        final String username = json.getString("name");

        https://packages.atlassian.com/public/com/atlassian/jira/jira-rest-java-client-parent/

         

        Stacktrace

        h.plugins.jira.JiraRestService#getIssuesFromJqlSearch: jira rest client get issue from jql search error. cause: RestClientException{statusCode=Optional.absent(), errorCollections=[]}
        org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.
        at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360)
        at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487)
        at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192)
        at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:34)
        at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:31)
        at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.getOptionalNestedField(IssueJsonParser.java:300)
        at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:234)
        at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:88)
        at com.atlassian.jira.rest.client.internal.json.GenericJsonArrayParser.parse(GenericJsonArrayParser.java:39)
        at com.atlassian.jira.rest.client.internal.json.SearchResultJsonParser.parse(SearchResultJsonParser.java:40)
        at com.atlassian.jira.rest.client.internal.json.SearchResultJsonParser.parse(SearchResultJsonParser.java:27)

        James Pressley added a comment - The removal of the name attribute seems to be causing jql to now fail using plugin  3.0.12   I can see the following line here which looks to be trying to still get it. Looks like the plugin needs to use a later version of the rest client. It currently uses 5.0.4 but the latest available is 5.1.6 https://docs.atlassian.com/jira-rest-java-client-parent/5.0.4/xref/com/atlassian/jira/rest/client/internal/json/JsonParseUtil.html#L192   Line causing issue final String username = json.getString("name"); https://packages.atlassian.com/public/com/atlassian/jira/jira-rest-java-client-parent/   Stacktrace h.plugins.jira.JiraRestService#getIssuesFromJqlSearch: jira rest client get issue from jql search error. cause: RestClientException{statusCode=Optional.absent(), errorCollections=[]} org.codehaus.jettison.json.JSONException: JSONObject ["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:34) at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:31) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.getOptionalNestedField(IssueJsonParser.java:300) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:234) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:88) at com.atlassian.jira.rest.client.internal.json.GenericJsonArrayParser.parse(GenericJsonArrayParser.java:39) at com.atlassian.jira.rest.client.internal.json.SearchResultJsonParser.parse(SearchResultJsonParser.java:40) at com.atlassian.jira.rest.client.internal.json.SearchResultJsonParser.parse(SearchResultJsonParser.java:27)

        Atlassian rolled out the change to JIRA Cloud for GDPR in the past few days, and this has completely broken
        the jira-plugin.

        See:
        https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944?utm_source=atlcomm&utm_medium=email&utm_campaign=kudos_comment&utm_content=topic#U1305250

        Craig Rodrigues added a comment - Atlassian rolled out the change to JIRA Cloud for GDPR in the past few days, and this has completely broken the jira-plugin. See: https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944?utm_source=atlcomm&utm_medium=email&utm_campaign=kudos_comment&utm_content=topic#U1305250
        Craig Rodrigues made changes -
        Assignee Original: Olivier Lamy [ olamy ] New: Radek Antoniuk [ warden ]
        Issue Type Original: Task [ 3 ] New: Bug [ 1 ]
        Craig Rodrigues made changes -
        Resolution Original: Fixed [ 1 ]
        Status Original: Fixed but Unreleased [ 10203 ] New: Reopened [ 4 ]

          warden Radek Antoniuk
          olamy Olivier Lamy
          Votes:
          4 Vote for this issue
          Watchers:
          18 Start watching this issue

            Created:
            Updated:
            Resolved: