codeforpdx / dwellingly-app

Application for property managers to communicate with social workers
48 stars 28 forks source link

Assigning a property to a user requesting access does not save the property assignment #817

Closed Chris-Boe closed 2 years ago

Chris-Boe commented 2 years ago

Describe the bug When you assign a property to a new user requesting access (and set them to Property Manager), the property selection is not saved in the database.

To Reproduce Steps to reproduce the behavior:

  1. Go to the dashboard and click "Add" on a user requesting access
  2. Set them to PROPERTY_MANAGER role
  3. Select a property to assign to them
  4. Click on Save (have network tab open to see the property ID getting sent to the backend
  5. Look up this user on the Property Manager list page
  6. Click on the user from the list
  7. Notice the property selected in step 3 is not shown on the page nor returned from the network request

Expected behavior New Property Manager should have property assigned

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

NickSchimek commented 2 years ago

I'm not seeing a place to enter a property. Looks like there might be two issues here?

Screen Shot 2022-07-18 at 0 24 27
Chris-Boe commented 2 years ago

@NickSchimek Looks like you might be looking at an old version of the app, when you select Property_Manager it should show a SearchPanel for Properties I think I was able to fix the Search Panel not showing up on my current branch and that's when I noticed the backend wasn't saving the update we're sending it. I'm almost done with my branch so once it's merged we can repro this and investigate!