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

Promote Dashboard Next #18348

Closed
sleshchenko opened this issue Nov 12, 2020 · 6 comments
Closed

Promote Dashboard Next #18348

sleshchenko opened this issue Nov 12, 2020 · 6 comments
Labels
area/dashboard kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system.
Milestone

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Nov 12, 2020

Is your task related to a problem? Please describe.

We have a pretty full MVP for Dashboard Next. It's a good time to start promoting it.

Prereq:

  • tests
  • docs

Describe the solution which should be implemented

Dashboard Next is only available on the Che installation on the {CHE_HOST}/dashboard path.

Describe the solution you'd like

Dashboard and Dashboard Next are both available on the cluster, but Dashboard Next is the default one.
So, when a user opens like che.openshift.io, he gets redirect to che.openshift.io/dashboard/next (the same with $che_host/f?url=)
Users are able to reach old dashboard with the direct link che.openshift.io/dashboard.

P.S. CRW as previously should use the existing dashboard, and at the time we decided Dashboard Next is ready - we just replace dashboard there.

Describe alternatives you've considered

The ideal solution would be:
Dashboard gets banner "Dashboard next now is available. Click here to try it out."
Dashboard Next gets the banner "Click here to save Dashboard Next as your default one."
Dashboard Next has someplace where a user is able to configure the default dashboard and return back to the old dashboard if needed.
^ but seems it needs more work which I'm not sure worths time.

Additional context

@sleshchenko sleshchenko added kind/task Internal things, technical debt, and to-do tasks to be performed. area/dashboard labels Nov 12, 2020
@sleshchenko sleshchenko added this to the 7.23 milestone Nov 12, 2020
@sleshchenko sleshchenko mentioned this issue Nov 12, 2020
35 tasks
@sleshchenko sleshchenko modified the milestones: 7.23, 7.24 Nov 12, 2020
@sleshchenko sleshchenko added the severity/P2 Has a minor but important impact to the usage or development of the system. label Nov 13, 2020
@dmytro-ndp
Copy link
Contributor

@sleshchenko: from Che QE team we have 8 Dashboard related tests at the moment:

Here the nightly E2E tests report which includes Dashboard and Workspaces tests: http://artifacts.ci.centos.org/devtools/che/che-nigthly-multiuser-all-test/279/report/site/failsafe-report.html

It would be nice to see more detailed changes list (PRs?) in Dashboard Next to help Che QE team to estimate E2E tests update effort.

@dmytro-ndp
Copy link
Contributor

@sleshchenko: do you have plan to update and to create more E2E tests on Dashboard side #16910?

@sleshchenko
Copy link
Member Author

As defined in the #18391 the prerequisite for it from QE side are Stages 0 and 1

@sleshchenko
Copy link
Member Author

@dmytro-ndp we want to cover all Dashboards functionalities with e2e testing but at this point there is no concrete plan with a timeline

@sleshchenko
Copy link
Member Author

The plan is changed. We're going to switch the dashboard to react-based one in 7.25

@sleshchenko sleshchenko modified the milestones: 7.25, 7.26 Jan 14, 2021
@sleshchenko
Copy link
Member Author

7.26 SNAPSHOT should already use new dashboard since #18549 and eclipse-che/che-dashboard#138 are merged 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

2 participants