Resolution field robustness #1218
Description
Resolution field updates seem to be a fragile:
- Until an issue is marked as resolved, the resolution field is not present on screen
- Once marked as done, resolution seems to become readonly, and switching the status back to in progress does not unlock it
I've had some transient errors on failing to update the "Resolution" field. That field is not visible on any of my screens until an issue is resolved. Then it does show, and it never changes. I think the errors are from 1) something about jbi failing to update a field that isn't there, and 2) a field that appears once an issue transitions to status "Done" -- but the resolution never changes again, even if the status changes away from done. You can see the latter on this screenshot of SYNC-4849:
Related issues:
- Attempt to update status before resolution on PCF project #1103
- Resolution was set to Done instead of value of mapping #1100
- Remove the resolution step for FOG migration #1102
Example of retried events that keep on failing (resolution is set to Cancelled but remains "Done")
Logs Explorer on webservices-low-prod:
resource.labels.container_name="jbi-retry"
jsonPayload.Fields.operation!="ignore"
