Commit Notifications Send Out Notifications Not for the Latest but the One Before that Commit
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Instead of receiving commit notifications for the most recent commit, Fisheye is sending out notifications for the one committed before the latest.
No errors reported in the logs. Commit notifications have been enabled for the repository and watches set correctly for all users.
Cause
Fisheye uses the current date and time to choose which changesets to include in a watch email. If the system clocks on the Fisheye and SCM server do not match, Fisheye may send out notifications for incorrect commits.
This has been reported as a bug here. Please watch it to be notified of its progress and feel free to comment there.
Resolution
Ensure that the system clocks on both Fisheye and SCM server have been synchronized.
Was this helpful?