When creating a task template with multiple status options, it appears that if you create one then remove it, it persists.
This is visible when you do an update task API call. The response contains the array of status options under custom_type → status_options. There remains any that I have deleted and one that is incomplete that I cannot remove.
Any ideas on how to manage this short of removing the entire task template and re-creating it?
Yes, as I recall this works the same way as custom field enum_options; it’s not possible to physically delete it but rather there is an enabled property that if set to false essentially works as a “soft delete”.
Hi @Marc_Bass , thank you for highlighting this observation.
Removed custom task status options do indeed persist, preserving their GIDs, however they are clearly marked with the "enabled": false property.
I believe the intention here is to make it technically impossible to break any data relations, for instance, when removing a custom status that is currently applied to existing tasks.
Moreover, since these custom types may be included in rules, the possibility of their hard removal would introduce the risk of uncertain rule states.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.