• 5
    • 1
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently fork syncing stops working if someone does a force push to the original repo. It seems very reasonable for fork syncing to stop working if that happens. However, the users who are depending on fork syncing should be notified via email and the inbuilt message box that it has stopped. It should not silently stop working.

            [BSERV-4495] Fork sync should notify when it stops syncing

            Ishwinder Kaur added a comment -
            Atlassian Update - 2 May 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Bitbucket Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues.

            Kind regards,
            Bitbucket Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 2 May 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Bitbucket Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues . Kind regards, Bitbucket Data Center

            I agree with the general approach to notifications for any reason and suggest to use the same messaging mechanism that we already have in place for when fork syncing stops due to removed permissions:

            Hendrik (Inactive) added a comment - I agree with the general approach to notifications for any reason and suggest to use the same messaging mechanism that we already have in place for when fork syncing stops due to removed permissions:

            I would generalize this to say email a notification list for any reason that the fork syncing stalls.

            Chuck Burgess added a comment - I would generalize this to say email a notification list for any reason that the fork syncing stalls.

              Unassigned Unassigned
              88e1ccbd67c9 Stephan Hoermann
              Votes:
              24 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: