JIRA REST API - missing parameters

I copied the class JsonParseUtil from jira-rest-java-client-core-5.1.6 and modified the function parsebasicUser to this:

@Nullable
public static BasicUser parseBasicUser(@Nullable final JSONObject json) throws JSONException {
if (json == null) {
return null;
    }

final String username = json.optString("name", "[" + json.getString("accountId") + "]");
    if (!json.has(JsonParseUtil.SELF_ATTR) && "Anonymous".equals(username)) {
return null; // insane representation for unassigned user - JRADEV-4262
    }

// deleted user? BUG in REST API: JRA-30263
    final URI selfUri = optSelfUri(json, BasicUser.INCOMPLETE_URI);
    return new BasicUser(selfUri, username, json.optString("displayName", null));
}

With this, my program runs fine.

All comments

Thomas Deiler_db00h3

Dear @Kuba_Janus ,

either it's a bug that went live with constant cloud deployment or the REST API changed. Have you tried to download the latest version of Atlassian's Jira-Java-Client?

So long

Thomas

https://confluence.atlassian.com/cloud/blog/2018/06/say-goodbye-to-usernames-in-atlassian-cloud

I'm getting the same problem using version 5.1.6 of

jira-rest-java-client-core

App_Umane

hello my comrade,

I am having the same problem, i m relieved that the problem is not only mine.

i am using the version 4.0.0

<dependency>
<groupId>com.atlassian.jira</groupId>
<artifactId>jira-rest-java-client-core</artifactId>
<version>4.0.0</version>
</dependency>

Please help.

Giuliano C.

Hey @Kuba_Janus,

As part of the European General Data Protection Regulation (GDPR), usernames have been deprecated from API calls and those will be identified by their Atlassian account ID (accountId), instead. This change has been announced in 2018 and had some reminders with some useful information:

https://community.developer.atlassian.com/t/announcement-reminder-on-removal-of-user-names/34111

Lastly, you can refer to our guide that shows you how to update the call, including the resources that required parameters like usernames.

I hope it helps! Feel free to raise a support case if there's any additional help the team could provide you, or if you want to share something specific that is related to your instance.

Cheers,

Giu

For me, I'm not even trying to get a username.
I have a Promise<Issue>
and I'm trying to do a .claim().

There's something in the back end for the claim() method that is calling
com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser

Narayanan Srinivasan

Me too. I can't claim an issue using the issueclient. In fact, I can still create tickets so there's something else that's broken.

Edit:
find -> claim

Through the API, I'm able to create a new Issue.

I get an error when I try to claim that same Issue.

I copied the class JsonParseUtil from jira-rest-java-client-core-5.1.6 and modified the function parsebasicUser to this:

@Nullable
public static BasicUser parseBasicUser(@Nullable final JSONObject json) throws JSONException {
if (json == null) {
return null;
    }

final String username = json.optString("name", "[" + json.getString("accountId") + "]");
    if (!json.has(JsonParseUtil.SELF_ATTR) && "Anonymous".equals(username)) {
return null; // insane representation for unassigned user - JRADEV-4262
    }

// deleted user? BUG in REST API: JRA-30263
    final URI selfUri = optSelfUri(json, BasicUser.INCOMPLETE_URI);
    return new BasicUser(selfUri, username, json.optString("displayName", null));
}

With this, my program runs fine.

Kuba_Janus

I have also made something similar Thanks for info!

next step will be replace jira-rest-java-client-core to owner impl

I've raised a separate question for the issue I'm having, which is a little different, but I think it has the same root cause.
https://community.atlassian.com/t5/Jira-questions/Jira-Cloud-REST-API-getting-an-error-on-Promise-lt-Issue-gt/qaq-p/1304283#M409162

@wwerner @Kuba_Janus Can you try this patch and see if it solves the problem: https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid/diff

This was submitted to the jira-rest-java-client plugin last year but was never merged.

@Thomas Deiler This fix https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid/diff needs to be merged to jira-rest-java-client.

That library is used all over the place, so without fixing that library, many things which access JIRA Cloud are now broken.

The latest release of jira-rest-java-client which is 5.16 does not have this fix, and is broken with the current API change. So this needs to be fixed and a new library needs to be released.

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.

@Ben Kelley that is true, but whether you like it or not, people are using workflows based on jira-rest-java-client plugin against JIRA Cloud.
I had a workflow working last week, and then due to the change in JIRA Cloud, the workflow broke this weekend.

I understand. Although there are often small changes and new features for Jira Cloud APIs that the Jira Server library didn't support, possibly that wasn't a problem for some people.

These changes by their nature were breaking changes though. It wasn't a decision we took lightly, so we sought to give as much notice as possible.

It is probably worth keeping in mind that there are a number of ways that Jira Server REST APIs (especially from an older release like 5.1) are incompatible with Jira Cloud REST APIs.

This looks good and works for me, too. It is superior to my quick fix as it

- does not deliver wrong data for the user name

- does change the BasicUser and User structures accordingly

- is test covered

So thumbs up!

https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid/diff

As software developers we fully understand that there are and will be differences in the developing products. However, in our case we are in need of some very basic statistics, that we mirror in an analytics elasticsearch cluster to get a superior overview of things going on and accessing the issue and workflow data to provide our customers accurate statistics and a solid foundation for billing.

I unterstand that there might be better ways (e.g. some cloud plugins) but this is the way it served us for years, coming from a long maintained server installation.

After successfully migrating to jira cloud we do not want to go back.

@Ben Kelley my suggestion would be to maintain a simple to use interface to the core data for programmers, e.g. not covering all the latest and greatest in both products, but enabling customers to access their data essential stored in jira (server or cloud).

For our user cases, the patched java client rest library does fulfill this need.

A last sentence: My experience with the atlassian team and dear fellow users was great, I was able to get my system up and working in one day. Thank you very much for the lively platform / users / support team.

Works like a charm for me.

https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93

See the patch mentioned in this thread.

Ducu Sultan_vrzyqy

Guys, I am trying to rebuild the JRJC library with the patch above (thank you for that), however, I am receiving this mvn error:

Failure to find com.atlassian.maven.plugins:artifactory-staging-maven-plugin:jar:1.0.3 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

Any idea what I can do here?

Clément_hby7sq

<repositories>
  <repository>
    <id>atlassian-public</id>
    <url>https://packages.atlassian.com/maven-external</url>
  </repository>
</repositories>

& same for plugins

Alexandru Giurovici

You don't have the correct plugin repositories.

<repositories>
    <repository>
        <id>atlassian-public</id>
        <url>https://m2proxy.atlassian.com/repository/public</url>
        <snapshots>
            <enabled>true</enabled>
            <updatePolicy>daily</updatePolicy>
            <checksumPolicy>warn</checksumPolicy>
        </snapshots>
        <releases>
            <enabled>true</enabled>
            <checksumPolicy>warn</checksumPolicy>
        </releases>
    </repository>
</repositories>

<pluginRepositories>
    <pluginRepository>
        <id>atlassian-public</id>
        <url>https://maven.atlassian.com/repository/public</url>
        <releases>
            <enabled>true</enabled>
            <checksumPolicy>warn</checksumPolicy>
        </releases>
        <snapshots>
            <updatePolicy>never</updatePolicy>
            <checksumPolicy>warn</checksumPolicy>
        </snapshots>
    </pluginRepository>
</pluginRepositories>

Ducu Sultan_vrzyqy

Thanks, guys!

pradit.parttime

Very Thanks, guys!

dt0b35

jira-rest-java-client

still needs to be merged:

And i get this: JSONObject["name"] not found from my JIRA connector for Eclipse which worked just fine until yesterday....

com.atlassian.connector.eclipse.internal.jira.core.service.JiraException: org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.


Atlassian Connector for Eclipse
3.2.5.v20150427

Eclipse
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500




eclipse.buildId=4.6.3.M20170301-0400
java.version=1.8.0_201
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Framework arguments: -product org.eclipse.epp.package.javascript.product -product org.eclipse.epp.package.javascript.product -product org.eclipse.epp.package.javascript.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.javascript.product -product org.eclipse.epp.package.javascript.product -data file:/C:/Users/willem.mulder/workspace/ -product org.eclipse.epp.package.javascript.product

com.atlassian.connector.eclipse.internal.jira.core
Error
Thu Feb 20 13:46:15 GMT 2020
com.atlassian.connector.eclipse.internal.jira.core.service.JiraException: org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.

com.atlassian.connector.eclipse.internal.jira.core.service.JiraException: com.atlassian.connector.eclipse.internal.jira.core.service.JiraException: org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.call(JiraRestClientAdapter.java:790)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.getIssues(JiraRestClientAdapter.java:315)
at com.atlassian.connector.eclipse.internal.jira.core.service.JiraClient.findIssues(JiraClient.java:368)
at com.atlassian.connector.eclipse.internal.jira.core.service.JiraClient.search(JiraClient.java:757)
at com.atlassian.connector.eclipse.internal.jira.core.JiraRepositoryConnector.performQuery(JiraRepositoryConnector.java:140)
at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.synchronizeQuery(SynchronizeQueriesJob.java:311)
at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.synchronizeQueries(SynchronizeQueriesJob.java:268)
at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.run(SynchronizeQueriesJob.java:199)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.atlassian.connector.eclipse.internal.jira.core.service.JiraException: org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.call(JiraRestClientAdapter.java:783)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.getIssue(JiraRestClientAdapter.java:248)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.access$3(JiraRestClientAdapter.java:247)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter$5.call(JiraRestClientAdapter.java:325)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter$5.call(JiraRestClientAdapter.java:1)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.call(JiraRestClientAdapter.java:746)
... 8 more
Caused by: com.atlassian.jira.rest.client.RestClientException: org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient.invoke(AbstractJerseyRestClient.java:89)
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient.getAndParse(AbstractJerseyRestClient.java:106)
at com.atlassian.jira.rest.client.internal.jersey.JerseyIssueRestClient.getIssue(JerseyIssueRestClient.java:133)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter$3.call(JiraRestClientAdapter.java:250)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter$3.call(JiraRestClientAdapter.java:1)
at com.atlassian.connector.eclipse.internal.jira.core.service.rest.JiraRestClientAdapter.call(JiraRestClientAdapter.java:746)
... 13 more
Caused by: 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:169)
at com.atlassian.jira.rest.client.internal.json.BasicUserJsonParser.parse(BasicUserJsonParser.java:26)
at com.atlassian.jira.rest.client.internal.json.BasicUserJsonParser.parse(BasicUserJsonParser.java:23)
at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.getOptionalField(IssueJsonParser.java:351)
at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:266)
at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:90)
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient$1.call(AbstractJerseyRestClient.java:111)
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient.invoke(AbstractJerseyRestClient.java:68)
... 18 more

Related: I'm writing up how to generate a client library in the language of your choice from our Open API spec. I'll link it here when it's done.

It won't be a drop in replacement for Server's JRJC (as it is not auto-generated), but it might be useful in terms of how you respond to future API changes.

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

Thanks @Ben Kelley ... however that's beyond me. Anyone out there capable of easily doing this for all us old-skool folk still using the Eclipse connector? Or perhaps just simply patching: eclipse\plugins\com.atlassian.jira.rest.client_3.2.5.v20150427\jira-rest-java-client-1.1-ide-m09.jar and making it available?

Currently looking at Tasktop Dev as an alternative but feel it too might be rusty...!?

CraigRodrigues

This document is good, but as you mentioned, it doesn't help people who have workflows and tools that use the existing libraries.

CraigRodrigues

@wwerner can you help me file a ticket against JIRA itself so that we can get someone at Atlassian to review and merge https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid/diff

I've never had to file a bug like this and am having trouble navigating the process.

@wwerner Can you try out version 5.20 of the jira-rest-java-client plugin and double-confirm the fix? @Kamal Cichy and @Andy worked on pushing this through and releasing a new version of the plugin: https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid/diff#comment-137009716

CraigRodrigues

@Ben KelleyDo you know which Atlassian team owns https://bitbucket.org/atlassian/connector-eclipse/src/rest/ ? That needs to be updated to use jira-rest-java-client 5.20 which @Kamal just released.

Maybe see this post from 2015 https://blog.developer.atlassian.com/discontinuing-ide-connectors-support/

@Craig Rodrigues Version 5.2.0 does work for me. The fix looks good.

@CraigRodrigues Looks like we're on our own here (along with anyone else still using IDE connectors to Jira Cloud!) Workflow's not completely fooked - I'm only really losing Mylyn's task-focus in Eclipse as a result! Let's try to keep eachother in the loop if we find a fix ok?

@wwerner can you look at https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/104/change-field-name-from-name-to-id-for/diff ? I found that I needed that, otherwise if I tried to create an issue with the Assignee prepopulated, the Assignee field would remain unassigned.

A suggestion here: If you develop against Atlassian Cloud APIs (including Jira) it is a good idea to subscribe to updates on https://developer.atlassian.com/. While APIs change all the time, breaking changes like this are not common, but they are announced well in advance.

This is particularly true if you develop a product or tool that integrates with Jira that you provide to 3rd parties.

@Ben Kelley Thanks for that pointer. I think a lot of people have been using these API's via the jira rest api libraries distributed by Atlassian, and these libraries are buried deep in people's workflows.

Specifically, a lot of Jenkins plugins which interact with JIRA use these libraries, so this is buried even deeper.

In collaboration with @dt0b35 I submitted this patch to the Jenkins JIRA plugin https://github.com/jenkinsci/jira-plugin/pull/213 which bumps up the jira rest api dependency and has some other fixes to deal with the API changes. That change has been merged, and the maintainer has released a new version of that plugin.

I've had people from at least 5 different companies contact me about that patch, so this API change has been affecting a lot of people.