try to update Reporter field from bulk api but can't update, example of API calls that were made
{"errors":[{"message":"You are trying to perform an unavailable operation for the selected 1 issues."}]}
Could the Reporter field be updated from the bulk api?
Is occupying the singleSelectClearableUserPickerFields option the right thing to do?
Correct request to update Reporter field with
curl --request POST \
--url 'https://pmo.atlassian.net/rest/api/3/bulk/issues/fields' \
--user 'test@test.com:123abc' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
"editedFieldsInput": {
"singleSelectClearableUserPickerFields": [
{
"fieldId": "reporter",
"user": {
"accountId": "712020:4f2-5fd63df962e0"
}
}
]
},
"selectedActions": [
"reporter"
],
"selectedIssueIdsOrKeys": [
"DEMO-12"
],
"sendBulkNotification": false
}'
Hi @Aquiles Lázaro Hernández -- Welcome to the Atlassian Community!
The documentation for the bulk edit endpoint: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-fields-post
Describes the Assignee and Reporter fields as examples which can be changed with singleSelectClearableUserPickerFields in a bulk edit operation.
However, the Get bulk editable fields one returns "a list of fields visible to the user to perform bulk edit operations": https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-fields-get
When I tried that one for example issues in my projects, it does return Assignee but it does not include Reporter. Thus at least for my site, Report is not supported.
Perhaps try that endpoint for your DEMO-12 issue to observe what it returns.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
Use the endpoint Get bulk editable fields
curl --request GET \
--url 'https://pmo.atlassian.net/rest/api/3/bulk/issues/fields?issueIdsOrKeys=DEMO-12&&searchText=reporter' \
--user 'test@test.com:123abc' \
--header 'Accept: application/json'
Get the answer
{"fields":[{"type":"reporter","id":"reporter","name":"Reporter","isRequired":true,"searchUrl":"https://pmo.atlassian.net/rest/api/3/user/recommend?context=Reporter&issueKey=DEMO-12"}]}
The error is that it passed as fieldId in field number 10118, but the id is reporter as it is in the response
I add the call to the bulk api correctly
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well done!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.