Details
-
Bug
-
Resolution: Timed out
-
Medium
-
2.5.4, 2.6.0
-
None
-
Severity 2 - Major
-
Description
Due to their distributed nature, the commit date of a changeset is not a reliable starting point for searching for revisions for watch notifications. If person A commits today and pushes today, the last sent changeset will be marked as today. If person B commits yesterday and pushes tomorrow, the commit date will be marked as yesterday so no notification will be sent when it is eventually pushed to the server.
Using an event based system, or using the incremental internal id of the changeset are 2 possible solutions
Attachments
Issue Links
- relates to
-
FE-3025 FishEye watch notifications can potentially not send changesets due to long running incremental slurps
- Closed