Don't Allow Jira Integration to Fail Based on One Field

What is the challenge?

I have a Jira integration that integrates many standard and custom fields. If there is an issue with one of those fields for whatever reason, the entire integration fails and will continue to do so even if there is nothing wrong with the rest of the fields.

What is the impact?

Data loss, systems are no longer in sync, and requires reaching out to customer support every time there is an issue for verification. Overall it is a huge time investment to get things working again.

Describe your idea

If there is an issue with a field (e.g. Description), but the rest of the fields are fine and have new updates, the data for those fields should still carry over via the integration. Instead, the data transfer for the entire record fails until the issue on the one field is addressed. Removing this limitation while still flagging errors in the integration log would allow for things to stay in sync as much as possible.