Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Item Requests #6

Open
3 of 10 tasks
htoo97 opened this issue Apr 2, 2020 · 3 comments
Open
3 of 10 tasks

Item Requests #6

htoo97 opened this issue Apr 2, 2020 · 3 comments

Comments

@htoo97
Copy link
Contributor

htoo97 commented Apr 2, 2020

Right now, we have the HomePage View that shows an all-text form for making item requests. We need to connect it to the backend to do stuff. This is a pretty comprehensive task that could get broken down.

  • Implement CheckOutRequest schema as specified in design doc
  • Make the HomePage view actually make new CheckOutRequests in the database
  • Make RequestReviewPage view to show all CheckOutRequests made in chronological order of Date Needed By
  • Link to that view from the admin page
  • This could be similar to the admin view we have now to show all existing items in inventory, where we can expand each row the show the details and do actions like approvals.
  • Enable approvals in that expanded view
  • Integrate SendGrid so that on approval, the system automatically sends out an email to the provided email and notifies them their request has been approved and provide the email of the approver (a TESC admin whoever approves that request) for them to reach out to and figure out logistics. For SendGrid integration examples, the decaf.live repo might be helpful.
  • Delete functionality for requests in the admin view

Stretch goals:

  • On approval, admin can select the quantity being approved
  • Figure out a way to deal with requests that we don't want/cannot approve for certain reasons. A possible approach would be to have an additional reason field in the schema that the admin can fill out when they review the request. If they set the approved quantity to 0 (meaning request is denied), they need to fill out the reason and we should send out an automated email saying the request was denied stating the reason.
@subhankar-panda
Copy link
Contributor

I think @caitlynmliu is working on the first 2 bullet points?

@htoo97
Copy link
Contributor Author

htoo97 commented Apr 4, 2020

reassigning @michl1001 to another issue then! also im assigning this to @caitlynmliu but feel free to remove yourself after working on the first two. ty!

@htoo97 htoo97 assigned caitlynmliu and unassigned michl1001 Apr 4, 2020
@caitlynmliu
Copy link
Contributor

[4/4/2020 Progress Update]: CheckOutRequests submissions are successful for users to check out a single object. Working on updating the form (front end) so users can input multiple items they want to check out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants