[
https://issues.apache.org/jira/browse/UNOMI-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-338:
------------------------------
Fix Version/s: 1.5.2
2.0.0
> Profile's "lastVisit" and "firstVisit" are not calculated properly
> ------------------------------------------------------------------
>
> Key: UNOMI-338
> URL: https://issues.apache.org/jira/browse/UNOMI-338
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.1
> Reporter: Noa
> Assignee: Taybou
> Priority: Minor
> Fix For: 2.0.0, 1.5.2
>
> Attachments: Screen Shot 2020-05-19 at 13.28.52.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The profile's "lastVisit" and "firstVisit" properties doesn't take into
> consideration that an event can be added with a custom timestamp.
> This can cause an OLD event to be considered as the "lastVisit" and a NEWER
> event as the "firstVisit".
> I attached a screenshot for an example -
> lastVisit -> April 18th
> firstVisit -> May 19th
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
