Summary
The current child functionality only allows one item per child. It should allow multiple. Show the items attached to the child on various lists.
Why change
This is a sticking point in the use of the child requests for at least some banks/partners. For instance, you might need both diapers and baby wipes, but you can't ask for that.
Details
When entering/editing a child, you should be able to choose multiple items [for example both Baby Wipes and Kids (Size 1)]. You currently can only choose one item.
There will obviously be model changes involved in implementing this, as the item is currently saved as an integer on the child model.
The children export will need to show the multiple items
The child index and the children information in the family should show the items -- for ease of review, as children age out of diaper sizes quickly
The child request index should show all the items attached to each child, and the child request functionality will need to be adjusted to take into account the multiple items.
Adding the ability to change the items needed from the child request page would also be grand, but it can be a followup issue
Notes
@cielf says: I took a look at the production data, and there are remarkably few cases where someone has used the loop hole of entering multiple kids with the same name.
Our most engaged banks don't make a lot of use of the child functionality, but to some extent they don't because it isn't good enough - and the reason mentioned most is the lack of multiple items.
Criteria for completion
Bonus round
Summary
The current child functionality only allows one item per child. It should allow multiple. Show the items attached to the child on various lists.
Why change
This is a sticking point in the use of the child requests for at least some banks/partners. For instance, you might need both diapers and baby wipes, but you can't ask for that.
Details
When entering/editing a child, you should be able to choose multiple items [for example both Baby Wipes and Kids (Size 1)]. You currently can only choose one item.
There will obviously be model changes involved in implementing this, as the item is currently saved as an integer on the child model.
The children export will need to show the multiple items
The child index and the children information in the family should show the items -- for ease of review, as children age out of diaper sizes quickly
The child request index should show all the items attached to each child, and the child request functionality will need to be adjusted to take into account the multiple items.
Adding the ability to change the items needed from the child request page would also be grand, but it can be a followup issue
Notes
@cielf says: I took a look at the production data, and there are remarkably few cases where someone has used the loop hole of entering multiple kids with the same name.
Our most engaged banks don't make a lot of use of the child functionality, but to some extent they don't because it isn't good enough - and the reason mentioned most is the lack of multiple items.
Criteria for completion
Bonus round