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

[Guided onboarding] Default the landing page based on the user's discovery question solution #148911

Closed
osmanis opened this issue Jan 13, 2023 · 5 comments
Assignees
Labels
enhancement New value added to drive a business result Team:Journey/Onboarding Platform Journey Onboarding team

Comments

@osmanis
Copy link

osmanis commented Jan 13, 2023

The landing page will soon have filters for each solution. The first time users land on this page from Elastic Cloud, we should default the filter to the solution that the user selected as part of discovery questions during sign up.

  • Search discovery question -> Search filter on landing page
  • Observability discovery question -> Observability filter on landing page
  • Security discovery question -> Security filter on landing page
  • Something else discovery question -> All filter on landing page

IMO I don't think we need to default the filter to the solution everytime a user hits the landing page. I think if we do it for the initial page visit from the Cloud console that should suffice to make it easy for users to find a relevant guide.

@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 13, 2023
@alisonelizabeth alisonelizabeth added enhancement New value added to drive a business result Team:Journey/Onboarding Platform Journey Onboarding team labels Jan 13, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/platform-onboarding (Team:Journey/Onboarding)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 13, 2023
@claracruz
Copy link
Contributor

claracruz commented Mar 13, 2023

@alisonelizabeth
I took a look at implementing this via applying a querystring parameter. Turns out we're going to need some help from our backend team to complete this task. i.e the querystring parameter will need to be applied backend side.

Currently the deployment resource endpoint looks like so ?acs=[kibana-URL/api/xxx/xxx/callback]&sp_login_url=[kibana-URL]

The task on the cloud backend-side would be to apply an additional parameter, e.g. cloud_discovery_use_case like so - ?acs=[kibana-URL/api/xxx/xxx/callback]&sp_login_url=[kibana-URL]?cloud_discovery_use_case=Observability

@HeranGa0
Following on from your quick look at this, is there further info we need to know please?

@alisonelizabeth
Copy link
Contributor

Thanks for looking into this @claracruz. Does it not work to simply add the query param to the code here and here?

@claracruz
Copy link
Contributor

@alisonelizabeth Oops I did not even realise we were doing this. Yes this works. 🤦

claracruz added a commit that referenced this issue Apr 4, 2023
#153367)

Related to #148911

This PR updates the guided onboarding landing page to filter solutions
based on user selected use case in cloud discovery questions. The value
will be passed as querystring parameter `?cloudDiscoveryUseCase=[value]`
from Cloud UI.

---------

Co-authored-by: Kibana Machine <[email protected]>
@alisonelizabeth
Copy link
Contributor

Addressed via #153367

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:Journey/Onboarding Platform Journey Onboarding team
Projects
None yet
Development

No branches or pull requests

4 participants