Giving a Team access to a repo does... nothing useful (BB-7113)

David Taylor avatarDavid Taylor created an issue

I'm trying to give a dev team outside my organisation read access to a few repos. As I'm not a member of their team, I can't give them Group access, but the "User" picker allows me to type in a Team name even though it doesn't appear in the dropdown.

Of course, adding a Team doesn't given the team members access to anything.

We should fix two things:

  1. Make it clear in the User picker that adding a Team won't work (or make it work)
  2. When we decide that we won't make it work, add a method to get permission from a Team to give one of its Groups permission. In my case I don't even need permission to browse the external Team's Groups - I just need the ability to add the group to my repo.

Comments (8)

  1. Jerome Guilbot

    Yes this is annoying. I have granted access to some of my team's repositories to another team. They did receive an email on their end saying they had now write access to the repos, but they can't do anything with it.

    Please clarify what the original intent was or implement David Taylor's solutions.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.