Replace custom field options" task fails instantly with no message (DELETE /field/{fieldId}/context/{contextId}/option/{optionId}/issue)

Hi,

The Replace custom field options operation starts a task, but the task always ends in FAILED within about 0.3 s, with progress: 0 and no message or result. Nothing is changed on the work items.

Request (run as a site admin in the browser; the same happens from our Forge app):
DELETE /rest/api/3/field/customfield_11520/context/12157/option/11453/issue?replaceWith=11454&jql=key%20%3D%20RMTT-1
Response: 303 → task, which then returns:
{
“id”: “60612”,
“description”: “Remove option 11,453 from issues matched by ‘key = RMTT-1’, and replace with option 11,454”,
“status”: “FAILED”,
“progress”: 0,
“elapsedRuntime”: 0
}
Without jql it fails the same way (description says “matched by ‘*’”).

What we verified

  • The field is a standard single select (com.atlassian.jira.plugin.system.customfieldtypes:select), created in Jira’s UI. The options were also created in the UI.
  • Context 12157 is mapped to the work item’s project (company-managed). The work item’s stored value is option 11453, and both options are in that context. The context has no default value.
  • The field is in the work item’s edit meta (operations: [“set”], both options allowed). PUT /rest/api/3/issue/RMTT-1 with option 11454 works.
  • The user has Administer Jira.
  • Bulk edit (POST /rest/api/3/bulk/issues/fields) with the same field and option completes successfully.

Questions

  1. Is this operation currently working, or is there a known issue?
  2. Is there a condition not in the documentation that makes the task fail? Or how can we get the reason, since the task has no message or result?

Task ids: 59508, 60612. We can share the site URL with Atlassian staff privately.

Thanks!

Hi @GoutamSingla1,

I reproduced it on a test site. A single select and a radio buttons field both went to FAILED with progress 0 and no message, whatever the jql, context or screens, while the same call on a multi-select completed and updated the issue.

So it looks tied to single-value option fields. It only failed when the JQL matched an issue that held the option.

The options doc only excludes options “created by Connect or Forge apps”. No public ticket turned up. I’d raise it with developer support as an Ecosystem Support Request, with both task ids and the site URL.

As the stand-in, bulk edit takes explicit keys, up to 1000 per request, so search first and batch. It needs Make bulk changes plus Edit issues. It emails people unless "sendBulkNotification": false is set.