Is it possible to always trigger a login when visiting our Bitbucket team website?

[Jimi Hullegård]

We have several repositories in Bitbucket, and I often surf directly to the team site in bitbucket (https://bitbucket.org/OUR-TEAM-NAME/). But this page doesn't require being logged in, so unless I am already logged in to Bitbucket I will not see our list of repositories (they are all private). So then I have to either manually click the "user menu" at the bottom left and then click "Log in", or surf directly to the url of one of our repositories that I remember the name of (or comes up in chrome autocomplete).

Since we have no public repositories, and the team settings has "Hide Bitbucket profile details" already checked, I really think that the team website should require (ie trigger) a login right from the start. Is there a way to achieve this? I want to be able to start a new browser session, surf to https://bitbucket.org/OUR-TEAM-NAME/, get logged in (it happens without any extra input from me when it is triggered) and then see all our private repositories right away. Is this possible?

[Daniil Penkin · Accepted solution]

Hello @Jimi Hullegård,

Unfortunately there's currently no way to enforce log in flow for that view. Your suggestion about triggering it for teams with hidden profile details sounds legit. Do you mind filing an issue for Teams component with the same description here so that it doesn't get lost and you are able to watch it?

As a workaround I can suggest you giving a try to repositories dashboard view – it requires (i.e. triggers) login and shows relevant repositories.

Hope this helps.

Cheers,
Daniil

[Jimi Hullegård]

Thanks @Daniil Penkin , that repositories dashboard workaround looks great! Bookmarking it.

I created this issue:

https://bitbucket.org/site/master/issues/19178/trigger-login-when-visiting-team-page-with

Maybe you could take a quick look and see if it looks up to standards, issue wise?

[Daniil Penkin]

The issue you created looks good to me, thanks! It'll be routed to the right team to consider such use case.

I'm glad the repository dashboard appeared useful :)

Happy to help,
Daniil