Teams

Bugsink’s Teams are a way of grouping users and associated projects together. This is useful in larger organizations where you might have multiple teams working on different sets of projects.

Remember that the primary unit of organization in Bugsink is the Project; that’s where the issues end up, where most of the access-management lives, and where notifications are configured.

Visibilty & Access

The main purpose of teams is to provide an additional layer of grouping when there are many projects. This grouping also aids in discoverability of Projects, because a project can be set to be visible or joinable by team-members only.

Here’s how it works:

• When a user is added to a team, they can see the existance of all projects in that team. All the team’s projects become visible in the “Team Projects” tab on the homepage, and a “Join” button is shown for each project. The user can then join the project, which will add them to the project and give them access to it.

• Team admins can change team settings, add projects to the team, and add/remove users from the team. They also are automatically “project admin” for all projects in the team.

• Team visibility is set to one of three options:

  • Joinable: anyone can join the team and see all projects in it.
  • Discoverable: the team is visible in lists, but there is no “Join” button. The idea would be that you can request to join (by walking over to the team admin and asking them, or sending them an email or chat).
  • Hidden: the team is not visible to non-members; you need to be invited.

Disabling Teams

In many smaller organizations teams serve no purpose; they can be globally turned off by setting SINGLE_TEAM to True.