- As of now the plugin cannot properly map to the “Timer” custom field. Under the hood the API treats it as a “Date” custom field and it will show up as such in the custom field mapping section. But the actual mapping will try to do the mapping as if for a regular “Date” custom field. It won’t cause any errors but you won’t achieve the desired mapping.
Known Limitations
Updated on December 18, 2025
