Bugzilla – Bug 73693
Resolve conflicts should halt sync until resolved
Last modified: 2018-10-04 14:41:04 UTC
Description of Problem : The user has many conflicts. The client continues to sync while the user is attempting to resolve a conflict. The user continues to be notified of new conflicts even though they are already attemptint to resolve the initial conflict. This leaves the user feeling like they are being barraged by messages and looking for a halt button. There is no halt button so the user may be tempted to simply close the client. Which of course will bring up the conflict resolver again once they launch the client again. Steps to replicate : 1. Create a bunch of conflicts between two shared clients while they are offline. 2. Start the clients up and allow them to sync. 3. Attempt to resolve the first conflict while the client is still syncing. Actual Result : The conflict notifications continue while the user is attempting to make a decision about the state of their data. This makes it difficult for the user to concentrate on the decision at hand. Expected Result : The user should not be notified of new conflicts while they are trying to resolve one conflict. This can be approached in several different ways. Its possible that halting the sync until the conflict is resolved is one way to approach this problem. Alternatively, the sync could continue and the files that are good can sync while the conflicts get logged silently. Later the user can see that there are conflicts and deal with them appropriately.
Moving to SP1
Arul, take a look at this sync issue
Sync cannot be stopped since the new updates has to be received form server. And also out of bound conflict resolution need to be honoured.
Closing this bug as per Comment3.Please reopen if you find any issues.