[Search Sessions] Time range change tour

[Dosant]

Part of #83640

Finalizing copy for the tour:

1. Is a search session will be accessible to anyone in that space? So the person viewing this (for the first time) might not be the person who saved the session?
2. Will we know if the time range was previously relative (but is now absolute)? And so will this show regardless if it was relative or absolute?
3. Is the primary purpose of this to forewarn them about changing filters/time since it will likely be a long-running session? Or is it about changing from relative time to absolute time?

Gail, let me know if I missed any of our questions.

Originally posted by @mdefazio in #89703 (comment)

cc @gchaps

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[Dosant]

@mdefazio,

Is a search session will be accessible to anyone in that space? So the person viewing this (for the first time) might not be the person who saved the session?

User sees only search sessions that they created

Will we know if the time range was previously relative (but is now absolute)? And so will this show regardless if it was relative or absolute?

It would be possible to show it in case the time range has actually changed. A bit tricky though.

Is the primary purpose of this to forewarn them about changing filters/time since it will likely be a long-running session? Or is it about changing from relative time to absolute time?

I thought that the primary reason is change from relative to absolute:

1. You've saved a search session with a time range now-15m.
2. Opened it the next day
3. It is important that results are not now-15m anymore, but pin pointed to that point in time when you've started the search.

[ryankeairns]

Linking this as a feature that would potentially benefit from user profiles - #17888

[gchaps]

Worked with @mdefazio on the text and came up with this suggestion:

We adjusted the time range...

The new range reflects the time you started your search.
Changing the time or filters will re-run the session.

Got it

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.