For example, a computed field without a UI will not have a useful way for the user to act on a conflict; and it is computed, the new value being saved is going to be the correct one. There should be configuration, or an alter hook, to allow specific fields to be skipped, or always use a specific strategy.
The example for this on Drupal.org is field_issue_last_status_change.
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
No activities found.