Open cloutid opened 1 year ago
Hey! This should clear things up: https://community.atlassian.com/t5/Jira-Software-questions/JIRA-REST-API-cant-get-account-id-to-create-issue-with-requestor/qaq-p/1759905#:~:text=Account%20IDs%20are%20a%20feature,api%2F2%2Fuser%20endpoint.
As a workaround, I used custom fields
to set the assignee name.
Good day, we've just upgraded to Splunk 9.x and we then updated to version 2.0.11 of this addon.
Just now started to realise that I can no longer create jira tickets with an assignee since it's requiring an id which our jira server doesn't use.
error message: HTTP Error=400, content={"errorMessages":[],"errors":{"assignee":"expected Object containing a 'name' property"}}"
i've tried all options available from our jira server; fullname, username and email.