Consider remembering team selection when visiting pages like workspaces

[gtsiolis]

Problem to solve

Following up from #10309, currently when visiting pages like workspaces, the team scope selection changes back to the personal account unnecessarily, as users may work inside a team most of the team and never use their personal account for adding projects, etc.

This could require users to perform more click actions to get back to their team or project they were working on before switching to workspaces, etc.

Cc @AlexTugarev because #10309 (review).

Proposal

Consider remembering the team selection when visiting pages like workspaces.

[aboqasem]

Hi! Do you mean this issue?

Team.Selection.mov

And also, is it intended to send users to the Projects (not Workspaces) page when they switch to team from Workspaces page?

[gtsiolis]

Do you mean this issue?

@aboqasem Yes, exactly.

And also, is it intended to send users to the Projects (not Workspaces) page when they switch to team from Workspaces page?

@aboqasem Correct, the team menu on the left is intended to be used for switching to projects for your personal account or any other teams you may be part of, concretely separating and providing a single point of access for the (global) workspaces list.

🍊 🍊 🍊 🍊

In case it's not clear enough from the issue description, the proposal here is to keep the selected team scope on the left menu intact and not fallback to your personal account when navigating to other pages like /workspaces since many users may not be using the product for developing for any personal projects but mostly collaborate with others or shared projects within a team.

Even when working with multiple teams or just a personal account, moving between workspaces and projects should be as frictionless as possible without requiring users to perform two click actions to get back to their team. Instead, helping users get back to the corresponding team from the workspace context (#5125) sounds better.

FWIW, we've experimented with separating the workspaces for teams and projects, but we reverted this change as it was more confusing than helpful, see #7604. Instead, we plan to focus on improving the workspaces list by introducing better filters (#8419), and more.

[aboqasem]

Thank you for the elaboration, @gtsiolis!

FWIW, we've experimented with separating the workspaces for teams and projects, but we reverted this change as it was more confusing than helpful, see #7604. Instead, we plan to focus on improving the workspaces list by introducing better filters (#8419), and more.

I made sure that determining the team is not just from the URL. So /workspaces would also be aware of the current team.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.