-
-
Notifications
You must be signed in to change notification settings - Fork 471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assignee field while creating jira ticket fails with 400 #373
Comments
Hi! Thank you for taking the time to create your first issue! Really cool to see you here for the first time. Please give us a bit of time to review it. |
Assignee and Reporter need to be user IDs not usernames
|
It seems the user you're using to authenticate the call doesn't have the Assignable User permission or the fields are not in the Issue Create screen. @Dynatrace-Adam-Gardner the User ID (account-ID) is required only on the Cloud version, on Jira On-Prem is the Username value |
…porter by accountID instead of username since it is deprecated in Jira cloud
@benjivesterby, @andygrunwald I think this issue is resolved and can be closed Best. |
@manuelbcd Sounds good |
Describe the bug
When I try to assign a ticket to some while creating it, zapi fails with 4000 bad request.
jira create API payload log looks like this:
"fields":{"assignee":{"Password":"","name":"svc.koalat-jira"},"issuetype":{"name":"Test"},"labels":["MyMy"],"project":{"id":"23432"},"reporter":{"Password":"","name":"fgvg.rtf"},"summary":"TestVoid"}}
but I get a 400 error with msg like this:
{"errorMessages":[],"errors":{"assignee":"Field 'assignee' cannot be set. It is not on the appropriate screen, or unknown."}
To Reproduce
create a ticket with assignee field as
assignee
Expected behavior
should create the ticket
Your Environment
Include as many relevant details about the environment you experienced the problem in
go version
): latestThe text was updated successfully, but these errors were encountered: