✔ Claimants' names not saving properly on the rebuild admin site when there are 3 or more Claimants' names
Completed by Nafiseh A.
- Assigned to
-
Harsh P.
- Notes
-
Hi
,
Morgan
I noticed that for disputes where we need to add claimants' names manually on the rebuild admin site when there are 3 or more claimants' names, the names are not saved properly on the system. When the names are entered and saved, they are all automatically changed to the very last name entered.
When I add the names the second time, the names are saved properly.
I wonder if we could resolve the issue.
Thanks,
Nafiseh
Further to the description above, could you please ensure this is resolved before we launch the new production environment on Monday. Note that this was reported on rebuild.investoratatelawguide.com.
I'm not sure if this issue is resolved on staging.investorstatelawguide.com and will be resolved when you deploy that version of the application to the production environment.
Thanks,
Morgan
We have checked and found that it is working fine on staging.islg. We haven't checked on rebuild.islg. But, We are sure that we haven't changed anything on rebuild.islg.
Could you please check again ?
The issue still exists on the rebuild admin site. I checked staging.islg as well, and I had the same issue as you see in the video below. Please note that this happens only when I need to add a new claimant name i.e. when I create a new claimant name in the Claimant(s) field.
Thanks,
Nafiseh
This is an application issue that needs to be tested on the staging.investorstatelawguide.com site. Could you please test if the issue is present there? If it works on staging, this issue should get resolved when the new production environment it deployed on Monday.
Thanks,
Morgan
The video above is the test on staging.investorstatelawguide.com and the issue exists there as well.
Thanks,
Nafiseh
Note that
Thanks,
Morgan
This issue is resolved on both rebuild.islg and staging.islg.
The issue is resolved on the rebuild.islg. I could not check staging.islg due to the server issue. I'll mark this complete once I am able to check it on staging.islg as well, and make sure the issue is resolved on staging.islg.
Thanks,
Nafiseh
The issue is resolved on staging.islg as well. I'll mark this to do as complete.
Thanks,
Nafiseh