Recent activity not updating

Issue #14156 resolved
Akash Anand
created an issue

"Repo activity is currently unavailable". Not able to see commits in Recent activity.

Official response

  • Jarred Colli staff

    Hey Bitbucket Friends,
    Sorry for letting this thread go conspicuously silent for so long. We've been having a long discussion about the Recent Activity feed because we're reworking the entire BB application to manage personal data better in keeping with GDPR regulations (hooray!). Basically, the Recent Activity feed needs to be rebuilt because of how it's architected, and how it manages personal data, and so we're taking it offline for now while we work through our personal data management changes. I apologize for the inconvenience, we're really working through a lot of data management changes. Please rely on the commits page for now until we get a chance to circle back.
    Your Bitbucket PM friend, Jarred

Comments (26)

  1. Jarred Colli staff

    Hey Bitbucket Friends,
    Sorry for letting this thread go conspicuously silent for so long. We've been having a long discussion about the Recent Activity feed because we're reworking the entire BB application to manage personal data better in keeping with GDPR regulations (hooray!). Basically, the Recent Activity feed needs to be rebuilt because of how it's architected, and how it manages personal data, and so we're taking it offline for now while we work through our personal data management changes. I apologize for the inconvenience, we're really working through a lot of data management changes. Please rely on the commits page for now until we get a chance to circle back.
    Your Bitbucket PM friend, Jarred

  2. Ansariel Hiller

    Erm seriously? The GDPR should be the reason for this? What personal data does it use other than what is already displayed in the commits page? And being the devil's advocate: Shouldn't the commits page be disabled as well in that case? Because what if somebody forks my repository but I don't want me name to be shown in their commit history?

  3. Log in to comment