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

[UX] Instead of error message "you are not allowed to start more workspaces", ask user if they want to switch to open workspace or close all workspaces in order to open this new one #21359

Closed
nickboldt opened this issue Apr 27, 2022 · 3 comments
Assignees
Labels
area/dashboard area/factory/dashboard Issues related to factories frontend (che user dashboard side) kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Milestone

Comments

@nickboldt
Copy link
Contributor

Is your enhancement related to a problem? Please describe

If you have an existing workspace running, and attempt to open a new one (assuming the default 1 running workspace per user has not been overridden by adminstrator at install time), you get an error message.

But as a user, it would be WAAAY smoother if instead of being told "you did something dumb" I was instead prompted with calls to action:

Would you like to close running workspaces?
Or would you like switch to your running workspace, so you can save/commit changes?

Describe the solution you'd like

On the https:///dashboard/#/load-factory page, provide me useful calls to action, which would be clickable links to either:

  • open the currently running workspace (if only one found, or else link to /dashboard/#/workspaces if more than one)
  • close the currently running workspace (if only one found, or else link to /dashboard/#/workspaces if more than one)

Describe alternatives you've considered

Continue to throw errors and make users figure stuff out the hard way.

Additional context

No response

@nickboldt nickboldt added kind/enhancement A feature request - must adhere to the feature request template. area/dashboard area/factory/dashboard Issues related to factories frontend (che user dashboard side) labels Apr 27, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Apr 27, 2022
@amisevsk amisevsk added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels May 2, 2022
@ibuziuk ibuziuk added sprint/next severity/P1 Has a major impact to usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Aug 4, 2022
@ibuziuk
Copy link
Member

ibuziuk commented Aug 4, 2022

Raising priority based on the retrospective discussion + adding the sprint/next label

@l0rd
Copy link
Contributor

l0rd commented Sep 1, 2022

@dkwon17 can we close this issue? I am asking to decide if we can include it in 7.53 release notes

@dkwon17
Copy link
Contributor

dkwon17 commented Sep 1, 2022

Oops, yes, this issue can be closed, fixed by eclipse-che/che-dashboard#607

@dkwon17 dkwon17 closed this as completed Sep 1, 2022
@l0rd l0rd added this to the 7.53 milestone Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard area/factory/dashboard Issues related to factories frontend (che user dashboard side) kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

No branches or pull requests

6 participants