Closed portoren closed 1 year ago
Thanks for the submission @portoren I saw this issue occur in a customer account. Glad you are able to track it down. This is related but not identical #52
Here is how we are going to handle this...
We want to NEVER save an absolute time window (one with a SINCE AND an UNTIL clause) -- We should raise an error if that is attempted.
We will consider renaming the five minutes ago entry in the time picker to simply say "NOW". This will mean that the time picker will always be setting the point in time
. Then the measure_time
will be a lookback
form the point in time.
NOTE let's consider raising an error if the user tries to:
UNTIL
clause.ago
statement
We should disallow theseLet's also consider putting a label above the time picker such as "reference point in time"
FYI @Sandeep10parmar
Please also add the "version found in" in the report.
@portoren Any more estimate on how long it may take to work on this?
:tada: This issue has been resolved in version 1.7.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Description
When a time window other than the Time-Picker default is selected, for example, "60 minutes ago", all touchpoints that did not have measure_time are temporarily calculated from the Time-Picker selection (SINCE 1668428490 UNTIL 1668428790). This change becomes permanent if the Touchpoints GUI editor is opened and the “Save Update” button is clicked.
Steps to Reproduce
The touchpoint graphic editor opens and clicks on the “Save Update” button.
The Pathpoint is reloaded with the Time-Picker in its default selection and the graphical editor of touchpoints is opened. It is evident that all the touchpoints that did not have a custom measure_time have been modified:
Expected Behaviour
Touchpoints GUI editor should not save changes in measure_time with Time-Picker effects.
Relevant Logs / Console output
Your Environment
Additional context