[Fleet] Show dates filter for "Future Timestamps" under agent Logs tab on navigating to Logs Stream changes to default value "Last 1 day".

[amolnater-qasource]

Kibana version:
Kibana:7.11.0 BC4 Cloud environment

Elasticsearch version:
Elasticsearch:7.11.0 BC4 Cloud environment

Host OS and Browser version:
Windows 10, All

Original install method (e.g. download page, yum, from source, etc.):
7.11.0 BC4 Cloud environment

Preconditions:

1. Artifacts for 7.11.0 BC4 Agent should be available.
   Link used: https://staging.elastic.co/7.11.0-c9f0a1f5/downloads/beats/elastic-agent/elastic-agent-7.11.0-windows-x86_64.zip
2. 7.11.0 BC4 Cloud environment should be available.
   Build Details:

    BUILD: 37776
    COMMIT: efd7b70e2803294a95395629dee55c89441d742a

3. Agent must be deployed using default policy having system integration.

Steps to reproduce:

1. Login to Kibana cloud environment.
2. Navigate to Fleet>Agents>Logs tab.
3. Set Show dates filter to "Next 1 hour" and observed no logs.
4. Click "Open in Logs" link.
5. Observed that Show dates filter is updated to default value, that is- "Last 1 day".

Reference ticket Id:
#83356 (comment)

Actual Result:
Show dates filter for "Future Timestamps" under agent Logs tab on navigating to Logs Stream changes to default value "Last 1 day".

Expected Result:
Show dates filter for "Future Timestamps" under agent Logs tab on navigating to Logs Stream should not change.

Screenshots:

What's working:
Show dates filter for "Past Timestamps" under agent Logs tab on navigating to Logs Stream is not changed.

What's not working:
N/A

Logs:
N/A

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[manishgupta-qasource]

Reviewed & Assigned to @EricDavisX

[EricDavisX]

@jasonrhodes does this relate to the component's overall expectation, in the way we've implemented it in Fleet side?

[EricDavisX]

@amolnater-qasource @manishgupta-qasource I recall talking about this, did you check for dupes to make sure it wasn't logged? Just asking. thank you!

[amolnater-qasource]

Hi @EricDavisX
We have verified and confirm you that this issue is not reported before.
Thanks
QAS