[ATLAS-4924] When client and server are on different timezones, searchFilter gives incorrect results using timerange operator.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.0.0, 2.3.0
• Component/s: atlas-core
• Assignee: Priyanshi Shah
• Reporter: Priyanshi Shah
• Created: 1 week ago 09:48
• Updated: 1 week ago 13:07

Description

When client timezone is UTC and server is on PST timezone, search filters will process the result according to the system timezone i.e PST and hence, the results are wrongly fetched. This is an intermittent issue as if the entities were created according to PST timezones then the search filter could have fetched proper results.

Steps to reproduce:

Scenario : Using "Today" filter with timerange operator, also client and server are on different timezones say UTC and PST:

 

1. Create two entities in UTC timezones.
 For example: If Today is 18th Nov'24 set one entity createTime as "1731888000000" and other as "1731974399000" which are basically start and end time of the day.
2. Search that entity with its typedef and select "createTime" as attributeName and operator as "Time Range" and value as "Today".
 

Results:

Expectation: Both the entities should be fetched.

Actual: Only one entity is getting fetched having createTime as "1731974399000".

Issue Links

• links to: Review Request