raygdev
commented
1 year ago Possibly create a nested route for vin lookup in the repair order route on the frontend. Provide a repair order route on the backend that looks up based on a parameter for vin.
1) The user looking up by vin should have full access to any repair created by them based on vin. 2) if the user isn't the creating user, any considerably private information should be redacted for the request. 3) things that should be visible would be a line by line of repairs performed. No need for dollar amounts. 4) labor hours should be included for transparency. 5) vehicle should also be looked up and populated with the repair request.
As a user I want to be able to look up all repair orders by VIN (Vehicle Identification Number)
Acceptance Criteria
1) The user looking up the repair by VIN should be able to access all of the repair orders created by them with that VIN 2) The user should also be able to look up other repairs that were made on that VIN by other users 3) If the repair order doesn't belong to the user, some information should be redacted from the repair order 4) The user should not be able to edit a repair order that isn't theirs 5) The VIN should be validated when making the request 6) The user should be able to see a message if the validation fails 7) The user should be able to see a line by line breakdown of repairs performed 8) Each line should have a labor time and associated parts that were replaced