Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify favorites and landing page for multi-namespace setup #468

Closed
isc-tleavitt opened this issue Sep 6, 2024 · 2 comments · Fixed by #538
Closed

Simplify favorites and landing page for multi-namespace setup #468

isc-tleavitt opened this issue Sep 6, 2024 · 2 comments · Fixed by #538
Assignees
Labels
customer Based on customer feedback (as opposed to something identified by developers) enhancement New feature or request usability

Comments

@isc-tleavitt
Copy link
Collaborator

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.

@isc-tleavitt isc-tleavitt added enhancement New feature or request usability labels Sep 6, 2024
@isc-tleavitt isc-tleavitt added this to the Q3/Q4 2024 Targets milestone Sep 6, 2024
@isc-tleavitt isc-tleavitt added the customer Based on customer feedback (as opposed to something identified by developers) label Sep 30, 2024
@isc-tleavitt
Copy link
Collaborator Author

isc-tleavitt commented Sep 30, 2024

Just heard some customer needs pointing back to this as well. There have also been reports/observations of favorites not being added to new namespaces, which would be ideal to investigate at the same time.

@isc-tleavitt
Copy link
Collaborator Author

@isc-akadoo, overarching goals here and for #510:

Make navigation better out-of-the-box and make it easier to add navigation post-installation after new users, namespaces are added.

  • As a non-technical git-source-control user with limited IRIS-level privileges, I want to be able to add favorites to get to git-source-control pages (pull, web UI) so that I can navigate more naturally from the management portal.
  • As a git-source-control user in an instance with multiple namespaces configured to use git-source-control, where I only really use two namespaces, I don't want to have tons of links to namespaces other than those two populated automatically because it's confusing if they are.
  • As a git-source-control user in a instance with multiple namespaces configured to use git-source-control, where I only really use two namespaces, when I'm doing something in the git-source-control UI (Git WebUI, Pull), I want to be able to see the namespace context where I'm operating to be sure that I'm working in the right place and fix it easily if I'm not.
  • (reach, optional, maybe not really feasible) As a git-source-control user in an instance with multiple namespaces configured to use git-source-control, I want links to git to automatically follow the namespace I was already in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer Based on customer feedback (as opposed to something identified by developers) enhancement New feature or request usability
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants