How can I add 'assignee' to JIRA issue request via POSTMAN?

[Ghulam Murtaza]

No matter where I put the assignee parameter in the body of the request, it does not populate in the Issue that I'm creating in JIRA. I'm a bit new working with JIRA's REST API so my ticket request is pretty simple (not much custom fields at all -but Im working slowly getting there).

However, I believe the format/syntax is right because I'm not getting an error parsing JSON message error in the response. And the ticket is still being created in JIRA even when I have 'assignee' in the body of the request. Having the 'assignee would be a neat feature to have automatically generated through the request for notifications Service purposes.

Can't I place 'assignee' param go anywhere on this request? I've tried in a few spots with no luck.

{
  "fields": {
    "project": {
      "key": "QA"
    },
    "summary": "Failure detected",
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        {
          "type": "paragraph",
          "content": [
            {
              "type": "text",
              "text": "Failure has occurred in POSTMAN"
            }
          ]
        }
      ]
    },
    "issuetype": {
      "name": "Task"
    }
  },
  "assignee": {
      "id": ""
}
}

Which creates this ticket (Screen Shot):

[Carlos Faddul]

@Ghulam Murtazaif you are using Jira Cloud, you can put the accountId in quotes, like the example bellow.

  },
  "assignee": {
      "id": "21435654322fdgvsdfsd"

 Remembering that the assignee must have a license and permission to be assigned to the project.

I hope I helped you.

If this post was helpful, mark it as Accepted Accepted, so you can help others who may have the same difficulties.

If your question has not been resolved, please post again with more details.

[Marc Isikoff]

Similarly, I'm in a branching to find one issue using JQL then update the trigger issue's assignee from the one issue's assignee.

{
           "fields" : {
{{triggerIssue.assignee}} : { "id": "{{ issue.assignee.accountId}}" }
                          }
}

is invalid JSON and this is ironically in Server version