Broken slot/pickup application bell notification
Summary
After our 2018 christmas release to production the bell notification for pickup applications to empty slots stopped working.
Steps to reproduce
Go to some store page not being the responsible (store manager/BIEB) for it. Look for an empty slot. Apply for it by clicking on that slot and say "Ja" to whatever question appears. As a next step, a bell should get fired towards the responsibles of that very store. They will see that someone has applied and they are asked to go to the store in order to grant that slot to the applicant. The bell entry is yellow when appearing first time. When you click it, it turns white (is it? - not sure if it doesn't kept yellow until it was "solved") and you get directed to the store. As soon as one of the BIEBs grants the slot, the badge count of the bells decreases for all BIEBs and the bell and list entry gets deleted completely also for all of them. Several applications for slots in one store get gathered. Display count (1) can represent multiple applications for a single store. That said 2 would mean two stores with 1-n unconfirmed applications. The bells for a single store do get deleted when everyone get accepted/deleted.
What is the current bug behavior?
This bell does not get fired at the moment. There is no number-badge and no list entry. BIEBs are blind regarding slot-pickups notifications. It's slowing down their important work.
What is the expected correct behavior?
Minimum desired functionality: Have the list entry back without a red-(1)-notification and not in real time. The normal behaviour is described above. Before our christmas update this application process triggered (instantly?) a bell notification with a red number-(1) per store and an highlighted entry in the notification list for BIEBs.
Relevant error messages and/or screenshots
The bell keeps "silent" and doesn't show a number nur list entry.
Possible fixes
It's not working since the 24.12.2018 release to production and wasn't able to being tested in beta due to this functionality only available in production environment. Maybe take a look at the commits of 09.12.2018 and #a1442021
Thanks to @peter.toennies for most of these descriptions from a thread in #foodsharing-dev in Slack: https://yunity.slack.com/archives/C1T1ZM9A4/p1546439129002700