-
Notifications
You must be signed in to change notification settings - Fork 14
Reduce contact journal amount of days stored to 10 #815
Comments
Thanks for your enhancement request @Ein-Tim. We have created an internal ticket for it and will raise this topic internally. Corona-Warn-App Open Source Team |
The CWA 2.20 announcement says: "Display of increased risk shortened from 14 to 10 days Furthermore, as of version 2.20, the CWA only looks at the last 10 days for calculating the risk of infection and not the last 14 days as before. This is in line with current quarantine specifications. A red tile therefore automatically turns green again on the 11th day after the last risk encounter. As before, users cannot reset the red tile to green manually or by registering a negative test result, as they can still develop symptoms because of the risk encounter within these 10 days (more information in this blog)." so it certainly would make sense to shorten the number of days recorded in the Contact Journal correspondingly to 10 days. Also the number of days available to be exported to the health authority would be reduced to 10 days. |
Could you please mirror this to JIRA / take note: I wrote with a Twitter user, who was very confused that risk exposures disappeared from her contact journal. Turns out: The exposure was more than 10 days ago, thus it disappeared. Link to Twitter: https://twitter.com/der_nalin/status/1534998807393484802?s=21&t=SjuVCVy6zyCa6Tq03X5lpw |
@Ein-Tim thanks for forwarding this. I'll add this to the internal ticket |
As the CWA project went into ramp-down mode, I don't expect this feature to be implemented. I'm therefore closing this issue. |
Current Implementation
I can see today + the last 15 days in the contact journal.
Suggested Enhancement
Reduce the days stored to today + 10.
Expected Benefits
Be consistent with the check-in & exposure logging feature.
Background: corona-warn-app/cwa-app-ios#4324
Ping @thomasaugsten, is this planned?
Internal Tracking ID: EXPOSUREAPP-12221
The text was updated successfully, but these errors were encountered: