-
Suggestion
-
Resolution: Low Engagement
-
None
-
11
-
2
-
Both force push and synchronize->discard for forks with fork syncing enabled (which I'm assuming is basically just a force push under the scenes anyway) are dangerous operations that can permanently alter the version history in unrecoverable ways and which don't show up in the commit log.
It would be useful if the occurrence of such an event and the user who performed either of the actions was listed in the audit log.
We had a problem recently with someone incorrectly discarding changes when resolving a fork sync issue and we have been unable to track down who performed it so we can talk through the impact that had and provide more training.
Form Name |
---|
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