Minor change to endpoint for deleting custom field options

What is changing?

Minor change to an experimental endpoint to delete custom field options where the issue data clean up is now done asynchronously. However, there should be no impact to the existing functionalities as the option entity remains deleted synchronously, and the option will not the visible to the user (and will not be returned by the get options endpoint) after the synchronous HTTP request is completed.

Why is it changing?

As the number of issues which are updated can be an unbounded number, for a performant and reliable API, we need to perform the updates to issue data asynchronously.

What do I need to do?

No action is required.

By when do I need to do it?

The fix will be progressively rolled out starting on the 29th November 2021.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.