Issue #3739 resolved

Can no longer see non-favorite non-owned repositories

craigahobbs
created an issue

I'm ("craigahobbs") a member of "intego" (Intego User) account's "intego_developer" group. Previously, I could see all "intego" repositories from my "craigahobbs" dashboard. As of today I can no longer see repositories that are not already favorites. This makes it impossible to have new favorite "intego" repositories. I can't clone non-favorite "intego" repositories as well. I believe this was introduced today. This is a "big deal" for our team. Let me know if I'm missing something.

Thanks,

Craig

Comments (6)

  1. Nicolas Venegas

    Hi Craig

    We did rollout a change today to our permissions code that should have been transparent to users, so it sounds like we may have a bug in the new code.

    Would you mind giving me a list, even a partial one, of repositories that you expect to be able to access but now can't? You can email support@bitbucket.org to do so, if you wish.

    Regards

    Nicolas

  2. craigahobbs reporter

    (Reply via crai...@gmail.com):

    Hi Nicolas,

    I just imported all of our repositories except one so, from my personal account, I am unable to see all of the repositories except the one that wasn't recreated. Here is the list of repositories I should be able to see but do not:

    avbase avlib contentbarrier contentbarrier_webadmin fileguard genvdef_bd insdk installers intego_act2 intego_commonservices intego_libraries intego_metrics intego_network_filtering_lib intego_nke intego_statusitem intego_tools intego_widget netbarrier netbarrier_x5 netupdate panda_antivirus panda_management_console personal_antispam personal_antispam_tools personal_antispam_x5 personal_backup pre_serialization_tools remotemanagementconsole remotemanagementconsole_deployment rmc_v1 taskmanager vdefs_production_tools virusbarrier virusbarrier_admin virusbarrier_admin_plugins virusbarrier_databasemanager virusbarrier_ios virusbarrier_mas washing_machine washing_machine_mas

    Craig

  3. Nicolas Venegas
    • changed status to new

    Hi Craig

    I suspect this bug is affecting the automatic granting of permissions to a repository for groups with a default access level.

    For example, if the "bitbucket:dev" group has a default access level of "write" for new repositories in the "bitbucket" account, then when I create the repository "bitbucket/api", the "bitbucket:dev" group should have write access on the new repository, but it seems that is not happening (since today's change).

    Regards

    Nicolas

  4. craigahobbs reporter

    (Reply via crai...@gmail.com):

    Ok, I see what happened now. I deleted and re-created the affected repos via the REST API. Previously, when a repo was created it was assigned groups with appropriate default access. That is no longer happening hence why none of our users in our groups can access the repositories. So it looks like the bug is in the REST API.

    Craig

  5. Log in to comment