Time specifications within policies are not accurate

[tmberthold]

Description - What happened? *

Original Issue:
when creating policy with time span or evaluation time and operators "<=" or ">" [etc.] are used the restriction should consider the end of the day time so for example if we say be valid <= 14th it should be valid until 14th end of day

Expected Behavior *

Create a policy that requires operators to work properly within a certain time span

Observed Behavior *

Users are confused by the fact that their policy-times are not transformed correctly.

Steps to Reproduce

Steps to reproduce the behavior:

• Create policy with timespan operators using "<=" or ">" etc.

Context Information

No response

Relevant log output

No response

Screenshots

In the following example, the user expects the time to include 17.08.24 until EOD because of <=, but in fact however it is only until 16.08.24 at 10pm. The information provided by the user and the user's understanding do not match the way it is then evaluated.

Proposed Solution by RT

• Right now already: There is a display text that is currently the "abbreviated" local date, and the tooltip shows the raw JSON
• We want to fix the display text function.
• Only round to a local date, iff: In local time the date is exactly midnight
• For upper bound comparisons (<, <=) calculate the day minus one
• The display text should be in local time