Allow Donors to control the 'Reserved' Status of Items they have uploaded ⏸️

[camelPhonso]

Expected Behaviour

• [ ] Donors should be able to mark their items as 'Reserved' for a specific user
• [ ] Donors should be able to remove the 'Reserved' status from any item they have donated
• [ ] When an Item is reserved, all relevant conversations should receive an update confirming this

Current Behaviour

Currently the database schema allows for this functionality because it includes in the items table the following values:

• reserved (this name should be changed to is_reserved)
• reserved_by

However, these values are not connected to any feature in our codebase at the moment.

Steps to Reproduce

1. Log into Kindly
2. Visit your profile page (make sure you have uploaded at least one item for donation)
3. There is no option to mark your items as reserved

[sulphite]

!request

UI wise I plan to do one of the following (please @ me if you have thoughts about this!!):

• on the cards on the profile page, add a button to toggle reserved status, next to the edit and delete buttons. This could open a modal to add the user you are reserving it for ?
• OR just add the controls into the edit item page. I think this would be easier but less user friendly.

Then the relevant row in the DB will be updated with the change.

For the conversation update I don't have a plan just yet, will comment when I get the first part done

[github-actions[bot]]

🤖 meep morp!

Thank you for your contribution @sulphite - this Issue is assigned to you as requested ✨

🔎 Please keep in mind that in order to give everyone a chance to contribute Issues may be unassigned if they go stale. You will be warned if the Issue is marked as stale at any point.

🔎 Please review our documentation for guidance on:

• common Patterns we follow in the code base
• conventions set for commit messages and naming of functions, classes or files

💡 The core team is available for any help and will try to respond to any comments in this Issue or questions on discord as quickly as possible.

Happy coding ! 🦆

[sulphite]

After discussion the new plan is as follows:

• a user can "request to reserve" through a button on each item page
• this adds their userid to the requestedToReserve column
• (the owner of the item gets a system message about this; this could be a separate issue)
• in a user's donated items list, if anyone has requested to reserve an item there will be a button to control who it is reserved for
• the button opens a modal which displays all the reserve requests with individual accept/deny buttons
• accepting a reserve request updates the status of reserved and reserved_by in the database

[camelPhonso]

After discussion the new plan is as follows:

• a user can "request to reserve" through a button on each item page
• this adds their userid to the requestedToReserve column
• (the owner of the item gets a system message about this; this could be a separate issue)
• in a user's donated items list, if anyone has requested to reserve an item there will be a button to control who it is reserved for
• the button opens a modal which displays all the reserve requests with individual accept/deny buttons
• accepting a reserve request updates the status of reserved and reserved_by in the database

Hey @sulphite !

Thanks for posting this outline, the plan looks great. I know you discussed this for a bit with Nich and your plan is pretty sound but I also want to highlight another route you can choose to take, depending on how the issue progresses:

We can start by letting the donor of an item mark it as reserved for any user that has a conversation with them related to that item. We already have all the utils that handle finding conversations related to an issue and recovering the id of the partner in that conversation.

Once that feature exists we can then create a new issue to allow refugees to request for this item to be reserved. That request would trigger a system message to be sent to the donor in a conversation between them and the user who request the item.

That brings the issue down to:

• create a button to be displayed in the itemCard.tsx of each item in the donatedItemsList.tsx that allows the donor to reserve the item
• that button will let the donor select any user who has an active conversation with them about the item
• once a user is selected out of that list the item is marked as reserved and no longer available for inquiries

[sulphite]

Hey @camelPhonso thanks for the input! I think splitting it into 2 issues makes the most sense, so I'll get to work on what you suggested

[github-actions[bot]]

🤖 meep morp!

This Issue is now marked as stale because there has been no activity for a while.

🔎 The Issue will be automaticaly unassigned and moved to the Backlog if it doesn't receive new activity in the next 7 days.

💡 To unstale this Issue please push any commits that are ready or provide an update in the comments.

[github-actions[bot]]

🤖 meep morp!

This Issue is now marked as stale because there has been no activity for a while.

🔎 The Issue will be automaticaly unassigned and moved to the Backlog if it doesn't receive new activity in the next 7 days.

💡 To unstale this Issue please push any commits that are ready or provide an update in the comments.

[github-actions[bot]]

🤖 meep morp!

This issue has been stale for 7 days so it's being automaticaly unassigned and will return to the backlog.

💡 Once in the Backlog this issue will be available for anyone to take up - you can request it again if you have contributions ready to submit.

[github-actions[bot]]

🤖 meep morp!

This Issue is now marked as stale because there has been no activity for a while.

🔎 The Issue will be automaticaly unassigned and moved to the Backlog if it doesn't receive new activity in the next 7 days.

💡 To unstale this Issue please push any commits that are ready or provide an update in the comments.