Open jim-sheldon opened 5 months ago
I could not reproduce this locally. I suspect a routing issue.
@aimeehan1 I was unable to reproduce this issue. I've tired: 1) Log in as first curator 2) Create case with curator's comment 3) Log out and log in as another curator 4) Edit case by updating comment It worked both locally and on dev deployment.
From @aimeehan1:
I reviewed US case ID2 and edited content for accuracy. I added a Curator Comment as a Record of Change. However, when I tried to commit changes, I received an error message. So, I tried to remove my comment to see if that is what was being referenced as “body.” “response should NOT have a body”. However, this just gave me another error message: “socket hang up”. I had to select Cancel to get out of this screen. When I was back on the linelist dashboard, I received another error message.
Note: I am the second senior curator to go in and edit case ID2. Maybe that’s part of the problem? Individual cases can go through many rounds of edits and we need to make sure that a Record of Change (Curator Comment) is captured each time.
Also, JAS had edited this case before me, and included a comment, which I could not see when I went to edit the case.