Issue Summary

When multiple JSM SLA custom fields are deleted, some fields can remain in the custom field trash beyond the expected permanent deletion timeframe.

This is a bug in the delete custom field flow. The permanent deletion process does not always complete successfully when multiple SLA custom fields are being deleted together. As a result, affected customers may continue to see deleted SLA custom fields in the trash even after they should have been permanently removed.

Steps to Reproduce

1. Create or use a Jira Service Management project where issues have multiple SLA custom fields configured.
2. Delete multiple SLA custom fields so that they are moved to the custom field trash.
3. Wait until the fields are eligible for permanent deletion.
4. Review the custom field trash after the expected permanent deletion process has run.

Expected Results

The deleted SLA custom fields are permanently removed from the custom field trash once they are eligible for permanent deletion.

Actual Results

Some deleted SLA custom fields remain visible in the custom field trash after they are eligible for permanent deletion.

The delete custom field flow does not complete successfully for the affected fields and requires a product fix.

An error happens during the permanent delete custom field flow when multiple SLA custom fields are processed together.

Workaround

Currently there is no known customer self-service workaround for this behavior. A workaround will be added here when available.