Bug is created with correct summary and description, but the assignee remains unset. Tried both username and ID. Minimal fix:
Bug b=new Bug(); b.set('assignee','user'); b.send();
I encountered a similar problem recently and discovered that the issue was less about the client and more about the underlying API configuration. In my case, even though the code was correct, the assignment settings were not properly enabled in the server configuration. I ended up checking the permission scheme and the API documentation to verify if any additional headers or settings were required. It turned out that there was an overlooked configuration flag that needed to be set to allow assignment operations on bug creation.
Considering similar issues I’ve faced recently, it seems that the problem might be related to how the client is trying to update the assignee rather than a pure coding error. In my experience, fields like assignee often have additional handling on the server side, which might require specific updates or calls after the initial creation. It may also help to check for any custom field mappings in the JIRA settings that could be interfering with default behavior, ensuring the API is allowed to update the assignee during bug creation.