A user should be able to hide a boost and they should not see it again in any boost slots
Goal
A user should be able to hide a boost and they should not see it again in any boost slots.
What needs to be done
To facilitate a 'not interested' or 'don't show again' feature, we may need to implement a new table to store such data. The boost table would then need to join against this when querying.
QA
UX/Design
Adding to the dropdown of the entity menu (post menu).
Personas
Consumers
Experiments
Use the epic flag.
Acceptance Criteria
-
Implement rule Boost-22 - "A user should be able to hide a boost and they should not see it again in any boost slots" -
Implement new table to store the hidden entities for each user. Store the guid of the entity, not the boost -
Wire up to the Boost table via a join -
Frontend should display "Hide" button in the dropdown -
Limit the hide action to 5 (config variable) per day unless in Minds+ -
Integration test
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments
Edited by Mark Harding