store log: Main issue
Description
There is need for a full protocoll of actions from users in stores. This could allow more actions to store managers (deleting of entries) and allow transparency of actions
-
There are disputes about handling from store managers towards users. e.g.: not approving or removing from slots without information, in most disputes noone steps forward and aknowledges their actions but rather let's it fade away.
-
confirmation for pickup slots. It is unclear among store managers who is doing what and who confirmed whom, which could also lead to a dispute. Also it is difficult to find out among store managers who is doing this task. "I always have to confirm the foodsavers- my other store managers don't do anything" This complaint can't be proven in any way and it is one word against the other.
-
Singing in and out from pickups slots by foodsavers: sometimes foodsavers sign themselves out without looking for help, as this is not tracked there is no reliable information on who was signed in the slot in the first place.
-
Protocoll of deletion of entries on the store wall. as it is planned that store managers can "clean" their wall - there is no possibilty for foodsavers to prove or complain about misuse from store managers of deleting to much/harsh. If it is protocolled it can also be traced on who deleted which entry - to avoid problems like in 1). if 5 is done - there wouldn't be a need to have all those "joined the store" messages on the wall.
-
Follow up on request to join a store , approving /declining from a store or making a foodsaver on the springer list removing from springer list etc. "i did a request x weeks ago but wasn't approved" etc. "I am being denied access to the store.
Impact
foodsaver / store manager / ambassadors
Proposal
https://gitlab.com/foodsharing-dev/foodsharing/boards/1047653?milestone_title=Store%20log&
#556 (closed) Table and defines
#557 (closed) Log function
#558 (closed) Request to Store
#559 (closed) Request Declined
#565 (closed) Request Approved
#576 (closed) MOVED_TO_SPRINGER
#575 (closed) MOVED_TO_TEAM
#574 (closed) REMOVED_FROM_STORE
#573 (closed) LEFT_TEAM
#570 (closed) SIGN_UP_TO_SLOT
#569 (closed) SIGN_OUT_SLOT
#568 (closed) REMOVED_FROM_SLOT
#566 (closed) Delete from store wall
#577 (closed) ADDED_WITHOUT_REQUEST (DESCOPED)
#572 (closed) MADE_STORE_MANAGER (DESCOPED)
#571 (closed) REMOVED_AS_STORE_MANAGER (DESCOPED)
https://gitlab.com/foodsharing-dev/foodsharing/blob/master/src/Modules/StoreUser/StoreUserControl.php#L89 for #577 (closed),#572 (closed),#571 (closed) - quite nasty.
#567 (closed) Removed all Slots (DESCOPED)
BEFORE MERGE :
-
Data privacy needs to be updated. -
Create table on Database
IN SCOPE:
- entry is not generated for "Yellow ribbon" would solve (!663 (closed)) and make it obsolete
- Remove display of yellow "blabla has joined store"
OUT OF SCOPE (Features that are related but not part of this issue ):
- Allow wall post delete for store managers (follow issue if protocol implemented)
- Ask store manager / bot / Orga for reason on negative actions (e.g.: deleting wall posts, removing from slot , denying store entry)
- Show protocoll somewhere and how.
- Define who has access to the protocoll
- Rewriting Model to Gateway functions -> new issue
Links / references
would help solve #95 (closed) , #92 (closed) and #120 (closed)
Work in Progress
- Background implementation in Progress
How the select could look like with more information (names etc.) (Bot is the name of the user - not the role)