It's possible to have the same environment name across multiple namespaces. The Conda Store UI opens a new tab every time you open an environment. So you can end up with several open tabs that all have the same environment name and there's no way to distinguish between them.
Note: this is similar to but slightly different from #307, which is about putting the namespace name in the Create Environment form so that if you walk away from your computer and come back later, you know which namespace the form is for. This issue is about adding the namespace when you open an already created environment.
Value and/or benefit
If a user opens several environments with the same name (perhaps to visually spot check them for differences), they will not be able to tell which environment belongs to which namespace unless they keep a mapping (tab -> namespace) in their mind.
So the benefit of this enhancement is reducing the cognitive load for users operating in Conda Store deployments that involve multiple namespaces, especially when those namespaces contain environments that have the same name as environments in other namespaces.
Anything else?
Note also that this issue pertains to two separate parts of the UI:
The tab title
The tab panel
The limited screen real estate for the tab title makes it a more challenging problem to put the namespace there. That means that the lower hanging fruit is to put the namespace name in the tab panel.
smeragoel
commented
6 months ago
Feature description
It's possible to have the same environment name across multiple namespaces. The Conda Store UI opens a new tab every time you open an environment. So you can end up with several open tabs that all have the same environment name and there's no way to distinguish between them.
Note: this is similar to but slightly different from #307, which is about putting the namespace name in the Create Environment form so that if you walk away from your computer and come back later, you know which namespace the form is for. This issue is about adding the namespace when you open an already created environment.
Value and/or benefit
If a user opens several environments with the same name (perhaps to visually spot check them for differences), they will not be able to tell which environment belongs to which namespace unless they keep a mapping (tab -> namespace) in their mind.
So the benefit of this enhancement is reducing the cognitive load for users operating in Conda Store deployments that involve multiple namespaces, especially when those namespaces contain environments that have the same name as environments in other namespaces.
Anything else?
Note also that this issue pertains to two separate parts of the UI:
The limited screen real estate for the tab title makes it a more challenging problem to put the namespace there. That means that the lower hanging fruit is to put the namespace name in the tab panel.