You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until now the plugin pulled back workspaces without applying any
meaningful scope, so the list it showed was effectively the whole
deployment. There was no way to narrow it down or to deliberately choose
whose workspaces you wanted to see.
This hit administrators hardest. On a large deployment the list could be
huge, mixing together the workspaces of every user, with no quick way to
focus on a particular person, template, or state.
This change puts that choice in the user's hands. A scope selector
switches between just your own workspaces and every workspace you're
allowed to access, and the selection is remembered separately for each
deployment so it sticks the next time you connect. Alongside it, a
search box narrows the list by name, template, owner, or status,
including quoted multi-word values and a plain-text shortcut that
searches by workspace name. An explicit owner in the search always takes
precedence over the selected scope. Changing the scope or the search
reloads the list and regenerates SSH configuration to match what is
shown.
Deep links can now carry an owner as well, so a link to a workspace name
that several users share resolves to the right one instead of guessing.
When no owner is given the lookup stays unscoped, preserving the
previous behavior.
To keep the list manageable out of the box, it now defaults to showing
only your own workspaces. Anyone who relied on seeing everything can
switch the scope to all workspaces, and that preference is then
remembered per deployment.
- resolves DEVEX-372
- resolves DEVEX-374
0 commit comments