[Spaces] Default to existing solution view when creating a new space

[mdefazio]

Describe the feature:
When creating a space, it's sometimes missed that I need to select a solution view for the navigation.

Describe a specific use case for the feature:
When creating a new space, we should provide a default for the navigation style / solution view to avoid extra form requirements.
We should use the current space's solution view as the default for the new space.

---

Perhaps there was a previous conversation around discoverability of the solution nav that is driving this current behavior? Do we want to revisit this decision? Do we expect to eventually default to the Elasticsearch solution view rather than Classic?

Screenshot of create space form with empty solution view field

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[eokoneyo]

@ek-so @alexmarhaba Could you please help look into this, the initial understanding is that it'd be helpful to default the newly created space to the solution view of the current space the user is currently using.

[ek-so]

We should use the current space's solution view as the default for the new space.

@mdefazio maybe you could share some extra considerations please — why using current space's solution view and not the one that was selected for this deployment during the creation process?

[alexmarhaba]

I think this makes sense to help drive adoption of new solution views. @mdefazio to confirm, you're suggesting that the "Solution view" dropdown is by default set to the current space's solution view. So if the space is Observability then the solution view dropdown's value is set to Observability. The user can change it to another solution or to Classic.

[mdefazio]

@alexmarhaba That's correct.

@ek-so I think it makes sense to come from the current context of the user rather than the initial deployment choice. Some thoughts, but happy to hear another take:

• Assuming I made a choice on the solution nav, we should persist that choice.
• If it defaulted to a Classic nav and I switched it to a Solution nav, we would want to continue driving adoption of the Solution nav
• If it defaulted to the Solution nav and they switched it back to Classic, I think it could case a lot of frustration to force them to continue changing that back.
• If it defaulted to an option and I've never changed it or looked at it...do we want to force them to make this choice?

[ek-so]

@mdefazio sorry maybe I was not clear with the question. I guess I agree with Alex (and it turns out, with you as well 😊) that we need to stick to the primary solution user chose when creating a deployment. So:

1. I agree
2. Also agree
3. and 4. - Not sure which case you mean by "defaulted to Solution". If the deployment existed before the solution views got introduced, we don't default them to anything as far as I know, we keep them classic. So if you create a new space from there, we probably still have classic as default option in a dropdown. Maybe I'm overlooking smth here? 🤔

[mdefazio]

You're right. If I create a new deployment, it defaults to a solution view, no? I guess my point was just reiterating that if I switch it back to classic, we would want to have new spaces then default to classic.

And yes, if I'm in classic and I create a new space, we should default to classic still.

I think we're all in alignment. 😄

[alexmarhaba]

@petrklapka for when you're back, can we have an engineer take a look at this? It's not urgent but seems like an easy lift.