✔ Problem with Last updated time stamp
Completed by Paul M.
- Assigned to
-
Harsh P.
- Notes
-
Hi Morgan,
This is not an issue with migration, however I thought I should post this.
There is an issue with the date last updated/timestamp.
Thank you,
Irit
I believe the issue above is a problem with the application, rather than the data, so I'm moving this to-do to: ISLG Team Feedback - To be triaged - TOLOGIX - ISLG App Rebuild.
Thanks,
Morgan
Please note and resolve the issue above.
Thanks,
Morgan
Similar to what Irit posted re: Arbitration Rules, I've discovered the same issue under Disputes and Dispute Documents.
Thanks,
Paul
Morgan
This issue is resolved on rebuild.islg and staging.islg.
The issue hasn't been resolved as shown in the video below. I've checked both rebuild.islg and staging.islg. Many disputes and dispute documents still show the same "Last Updated" time which cannot be correct.
We resolved the issue. We haven't updated old data's data. You need to check with new data add/edit on both dispute & dispute document on rebuild.silg and staging.islg.
Irit and Nafiseh are uploading/updating arbitration rules and dispute documents on app.islg today.
Thanks,
Paul
This is correct now on app.islg.
Thanks,
Irit
The wrong last updated time stamp issue came back on app.islg admin site as shown in the video below. There are about 20 disputes showing the same last updated time (and by me). I only updated UN/0133.
I also experienced the wrong last updated timestamp issue on app.islg admin site as shown in the video below. There are about 40 disputes indicating the same last updated timestamp updated by me. I only updated IC/0492, IN/0059, IC/0160, and IC/0579.
Reporting another instance of incorrect last updated time stamp as shown below. I didn't update the disputes I've indicated below (not even possible to update all the disputes exactly at the same time as indicated).
Thanks,
Paul
Thanks,
Morgan
Thanks,
Paul
We have resolved issue on app.islg. Please check and verify now that it will be not happened again.
Paul
The issue is resolved, thanks.
Paul