Sure. Let’s say if a user wanted to make a list of 5 things to do as a subset from an existing bigger list of 20 things - and one of the chosen things they will want to do multiple times (coffee break).
The coffee break would be in the existing list, and the user wants to add it 3 times to the subset list.
I suppose instead of it being a list, the db could be designed as a single thing with a quantity field. However, this app uses the draggable elements plugin to reorder a list of things, which would break its’ functionality.