-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
When we import date variables, Optimize can only use the values for filtering if they match the Optimize date format specified as "yyyy-MM-dd'T'HH:mm:ss.SSSZ". It will accept and import other string formats for date variables, but any filtering for those variables will exclude results.
We should either reject variable values that don't match the correct format or attempt to normalise these values on import before we store them to Elasticsearch.
ATs:
- Date variables that don't match the expected Optimize format are either rejected or normalised before storage
- We allow missing/null values to be stored
- We include the expected date variable format in our documentation and make this clearer for users
This is the controller panel for Smart Panels app
[OPT-4014] Attempt to normalize date variable strings to Optimize compatible format
| Link | New: This issue is related to SUPPORT-8168 [ SUPPORT-8168 ] |
| Description |
Original:
When we import date variables, Optimize can only use the values for filtering if they match the Optimize date format specified as {{"yyyy-MM-dd'T'HH:mm:ss.SSSZ"}}. It will accept and import other string formats for date variables, but any filtering for those variables will exclude results.
We should attempt to normalise other string values on import and before we store them to Elasticsearch. If we cannot normalise them to the correct format, we should log an error/warn and store the value anyway. *ATs:* * Date variables that don't match the expected Optimize format are normalised before storage if possible * If not, we should store these values anyway * We include the expected date variable format in our documentation and make this clearer for users |
New:
When we import date variables, Optimize can only use the values for filtering if they match the Optimize date format specified as {{"yyyy-MM-dd'T'HH:mm:ss.SSSZ"}}. It will accept and import other string formats for date variables, but any filtering for those variables will exclude results.
We should either reject variable values that don't match the correct format or attempt to normalise these values on import before we store them to Elasticsearch. *ATs:* * Date variables that don't match the expected Optimize format are either rejected or normalised before storage * We allow missing/null values to be stored * We include the expected date variable format in our documentation and make this clearer for users |
| Mentioned Roles |
| Mentioned Groups |
| Status | Original: Open [ 1 ] | New: In Specification [ 10000 ] |
| Status | Original: In Specification [ 10000 ] | New: In Development [ 10312 ] |
| Assignee | Original: Joshua Windels [ joshua.windels ] | New: Johannes [ johannes.heinemann ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
| Assignee | Original: Johannes [ johannes.heinemann ] | New: Michael Schoettes [ michael.schoettes ] |
| Status | Original: In Review [ 10212 ] | New: In Test [ 10004 ] |
| Labels | Original: current_release | New: current_release next_release |
| Labels | Original: current_release next_release | New: next_release |