You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature will then lead to the issue to make a decision how the notifications should be stored. Because the list of notifications is meant to grow statically over time, this will lead to storage space and thereby performance issues.
Therefore I suggest to tackle the assumption of statically growing and establish a clean up logic. Such mechanism should simply tidy up old notifications, so the list does not get to big at any time. It could be based on time (like purge notifications older than 30 days) or absolute number (like keep the last 1000 notifications). I would recommend to take the absolute number approach. Despite it is incredibly easy to implement, it guarantees that there are never too many notifications stored (for the theoretically case that the users causes millions of notifications within the defined time range). Also does this approach makes sure there are always some notifications shown. Never mind if he wasn't active for a long time or simple does not trigger that many notifications.
User Story
As Chris I would like to see my old notification so that I am not getting confused
@weilbith Is this correct like this? Please correct if this is not.
Acceptance criteria
Tasks
The text was updated successfully, but these errors were encountered: