How do you report bugs on Java Client Library?

[Chris Picard]

I have tried to find the official bug report site for the Jira Rest Java Client Library and have not found one so i am reporting the issue here. I have more issues to report later so knowing were would be good, but the current issue is a blocker.

I am attempting to create a split operation that will break a current Issue into a new one. During this process I copy certain values including Assignee. However, the assignee that is returned when you get an issue has a null name field. I am assuming this is because of some privacy/security reason though you can still see the display name. The current JiraRest Java Client Library only lets you set an assignee in the issue builder based on the name. This should be replaced by at a minimum a by user id, but more preferable an option of id or email.

[Matt Doar _Adaptavist_]

https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview says "Atlassian no longer supports Jira REST Java Client library" so that's annoying. It sounds like the JRJC may never have been fully updated to handle the use of ids rather than usernames? Perhaps cloning the issue and modifying the clone might get you unstuck?

[Ollie Guan]

Hi @Chris Picard ,

The issue you’re facing is related to how the Jira REST Java Client Library interacts with Jira Cloud after the GDPR / accountId privacy changes. This is essentially a developer / SDK integration issue rather than a general product usage question.

I recommend posting your question on Atlassian’s official Developer Community, where Atlassian platform/SDK engineers and other developers are more likely to see it and provide code-level guidance:
https://community.developer.atlassian.com/

Why the Developer Community is a better place for this:

• It is Atlassian’s official community for developers, focused on REST APIs, SDKs, and app/plugin development;

• Your question is more likely to be seen by the maintainers of the Jira REST Java Client or related engineers;

• Other developers who run into similar GDPR / accountId / username compatibility issues will be able to find your post more easily via search.