400 http error when assigning issues about jira-client

[itaddams]

it should be {field :{"assignee":{"name":"user1"}}}

[bobcarroll]

The error message suggests that assignee is a string and not a dictionary. You would get this result if your JSON looked something like this {"assignee": "user1"} when it should be {"assignee": {"name": "user1"}}. The only way I could see this happening is if the editmeta data coming back from JIRA is wrong.

Can you try this instead?

tempIssue.update().field(Field.ASSIGNEE, Field.valueByName("user1")).execute();

That will force jira-client to send the value as a dictionary in the form of {"name": "user1"} instead of a string.

[v1v]

I'll give a go tomorrow morning and let you know the outcome.

Thanks rcarz

[v1v]

issue.update().field(Field.ASSIGNEE, Field.valueByName("robin")).execute();

Same error, I'm afraid:

400 Bad Request: {"errorMessages":[],"errors":{"assignee":"data was not an object"}}

Let me know if you need further details.
Thanks again

[v1v]

Atlassian JIRA Project Management Software Version: (v6.3.14#6345-sha1:47b2bb0)

[danjee]

Hello,
Thanks for the nice API.
I'm having the same issue when changing the assignee field.
My java code is:

User user = User.get(jira.getRestClient(), assignee);
issue.update().field(Field.ASSIGNEE, user).execute();

Adding a comment or making a transition in a workflow works.
Jira version is JIRA v7.1.1
Any idea?

Thank you

[danjee]

@v1v : did you get around this issue? Thanks

[danjee]

Also with

issue.update().field(Field.ASSIGNEE, Field.valueByName(username)).execute();

gave me the same error.
I will try to put tcpmon between the endpoints to see what goes trough the wire and hopefully see that is only my fault. If I use the jira-client in a standalone test application all goes well. My problem is in a custom jenkins plugin I want to make; when trying to update the assignee from a git comment. Maybe some other jar in the classpath ruins the rest call,even though it's not the case when adding jira comments or transitioning through the workflow.

[bobcarroll]

I was not able to reproduce this, so it would be very helpful to see the results of your capture.

[danjee]

The capture gave me nothing due to some intranet restrictions. I got around it by calling the Jira rest API directly. Maybe the issue is fixed with the changes in this release iteration and not on the Maven central release and that is why you couldn't reproduce it.

[matiasrosemberg]

I can't change the ASSIGNEE too,

public void addAsignee(String numticket, String user){
        try {
            System.out.println(jira.getIssue(numticket).getAssignee());
            System.out.println(jira.getIssue(numticket).getField(Field.ASSIGNEE));
            jira.getIssue(numticket).update().field(Field.ASSIGNEE, Field.valueByName(user)).execute(); //THIS LINE DOES NOT WORK
            System.out.println(jira.getIssue(numticket).getAssignee());
        } catch (JiraException e) {
            e.printStackTrace();
        }
    }

net.rcarz.jiraclient.JiraException: Field 'assignee' does not exist or read-only
at net.rcarz.jiraclient.Field.getFieldMetadata(Field.java:432)
at net.rcarz.jiraclient.Field.toJson(Field.java:535)
at net.rcarz.jiraclient.Issue$FluentUpdate.execute(Issue.java:171)
at abm.robot_automation.BotJiraV2.addAsignee(BotJiraV2.java:151)
at abm.robot_automation.App.main(App.java:16)

[imbyungjun]

In my case, Field.ValueTuple was cause of the bug.
In the FluentTransition.realExecute() method, it moves whole the entries in the member variable map fields to the local variable map fieldmap.
When fields contains a value a type of Field.ValueTuple, it doesn't move to fieldmap properly. So the fieldmap contains a entry that key is copied but value is null.

The workaround is passing the value as Map like this.

issue.transition()
    .field(Field.ASSIGNEE, ImmutableMap.of("name", assignee))
    .execute(TRANSITION_ASSIGN_ASSIGNEE);