Remove redirection to team context when previous context was a team

[gtsiolis]

Problem to solve

Back in #5854 and #5894, we redirected users to the last selected team when loading gitpod.io. Cc @AlexTugarev @jankeromnes

Also, we recently merged all workspaces lists into a single list in #7606. Cc @svenefftinge

This makes redirecting to the last selected team, less useful or practical, especially with the upcoming changes to allow users to start workspaces for any project or team from the workspaces and other pages, see #7564. 💡

See relevant discussion from discord. Cc @jacobparis

Proposal

Redirect to the new single workspaces list when loading gitpod.io.

[jacobparis]

Redirect to the new single workspaces list when loading gitpod.io.

This would effectively solve the problem for me and remove the need for any dedicated "workspaces" nav items. As long as there is a gitpod logo within arms reach I can click that and get where I want to be

[svenefftinge]

Proposal

Redirect to the new single workspaces list when loading gitpod.io.

I think this is already the case.

FWIW, I like @jacobparis proposal to add a workspaces button to the global nav on the right.
What do you think, @gtsiolis?

[gtsiolis]

I think this is already the case.

@svenefftinge There's a small edge case where if the exit page is a team or a project page, openining gitpod.io will redirect back to the team page (projects list) instead of the new single workspaces list.

Besides this, adding a global workspaces menu sounds great! 💯

🍊 🍊 🍊 🍊

Things to consider while making this change:

1. If Workspaces link is added on the right, consider hiding help links (Docs, Help) in their own dropdown menu or insie the user menu so that link weight remains balanced.
2. Consider moving the Workspaces towards the left side of the navigation if possible as usually more important elements are placed on this side. See F-Pattern[1][2][3][...]

[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.

[gtsiolis]

The existing behavior will become irrelevant and actually helpful once we make the changes in #8385. Cc @jldec

[jacobparis]

I can confirm the changes in #8385 solve the original concerns I had on Discord back in january

[gtsiolis]

Closing this as the issues described here are mostly no longer relevant after the updates in #8385 which have been already deployed on production. One small further improvement has been described in follow up issue in #10496.