[MGNLPER-48] Consider applying timezone into SearchQuery and SearchResults Created: 30/Aug/18  Updated: 22/Sep/22  Resolved: 22/Sep/22

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Periscope improvements
Team: AuthorX

 Description   

Currently, we actually get the time zone information from the user, however, we don't make use of it and instead simply convert it to localDate. Ideally we should be getting the time zone information from the users' preference and do the conversion with showing correct time zone values to the user and also make use of it in the SearchQuery(s).

The final JCR query should include time zones, as node modification dates have time zone information as well.

Value / business benefit: Date range filter in the Find Bar is in the user's own timezone. The time makes more sense to the user, feels more relevant.


Generated at Mon Feb 12 10:28:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.