1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #7891 open

Teams are not displayed in the Teams dropdown menu unless the user is an Administrator or Creator for the team (BB-9075)

Joseph Earl
created an issue
  1. Create a team
  2. Create two Bitbucket accounts
  3. Add one account as an Administrator for the team, the other as a Developer
  4. Log in to the Administrator account and click the Teams drop down menu, notice a link to the team is displayed under "Teams"
  5. Log in to the Developer account and click the Teams drop down menu, no link to the team is displayed (or the 'Create a new team' blank slate is shown if user doesn't belong to any other teams)

There seems to be no quick and easy way for a user who is not an Administrator for the teams to quickly switch and view those teams accounts.

Comments (15)

  1. Dan Bennett staff

    Can you see the team on your developer account's dashboard overview? We only enable the team admin link for the administrators but all members should be able to navigate to the team via their dashboard.

  2. Joseph Earl reporter

    Yes, from the dashboard overview I can see the team link on the developer's account below the repositories listing. What I would like is for the team link to be in the user drop down for everyone as it is for admins so the team page is easily accessible from everywhere: I find people spend most of their time on Bitbucket not on their dashboard. When I click the link in the drop down on the admin account it only takes to me bitbucket.org/teamuser so I don't really see why it is regarded as an admin link.

  3. Joseph Earl reporter

    If this as designed as you seem to indicate (please confirm) then I will convert this into a proposal to add links to teams from the drop down menu as that would seem more fitting.

  4. Dan Bennett staff

    Gonen Shoham, for what appears to be a superficial flaw this is a hard problem for us to solve without some costly effort.

    I'm only speaking for engineering here, but I feel comfortable telling you that we're currently in what you might call an "RFC" phase of looking at how our group management is implemented and identifying ways to pay down some technical debt (including the source of this bug). If the RFC pans out it will be followed by proper specifications, scheduling, design, implementation, etc but there is a lot of time and thinking between now and the hypothetical deployment of the new code.

    So, to answer your original question as to whether it will be resolved in the "near" future: no, most likely not for what most people might consider "near." However, that's not because we don't see this as a problem. We are very interested in resolving this and we will update this issue when we get closer to having something more concrete and are able to confidently say that it will be resolved in the near future.

  5. Log in to comment