Simplify favorites and landing page for multi-namespace setup #468
Labels
customer
Based on customer feedback (as opposed to something identified by developers)
enhancement
New feature or request
usability
Milestone
The common pattern in Health Connect Cloud is to have multiple dev namespaces. Our current git-source-control installation process creates a favorite link to each namespace, but really we should just create a single link and either (a) use the request context namespace, if possible, to determine namespace selection or (b) allow the user to drop in to the Git WebUI with no namespace context and support picking one right away, with a default selection of a namespace mapping to the current user's username if such a namespace exists. Really, even if (a) works, we should have support for (b) as well.
The text was updated successfully, but these errors were encountered: