Hi Martin :

As shown below, the three disputes below (IC/0308, IN/0131, IC/0525) have not been updated by myself or Nafiseh . It might have been updated by Gary.

image.png 64.8 KB • Download

ISLG admin site shouldn't randomly identify someone as the person who last updated it when in fact it is not that person. I am unsure about the other disputes on the screen capture (IC/0153, IC/0520 and IC/0608). Please investigate who in fact updated IC/0308, IN/0131 and IC/0525 and correct "Updated By."

Thanks,

Paul

Hi Harsh ,

Please investigate this issue and let us know why Paul and Nafiseh's names would appear on these records if they have not updated them on these dates.

I have created task https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/2201 for this. 

Thanks,
-Martin

Hi Paul   and Nafiseh ,

have you worked on any dispute document related that dispute ?

Cc Martin  

Hi Harsh ,

No, I haven't made any changes to these disputes.

Nafiseh

Hi Harsh ,

After speaking with Nafiseh , it is possible she worked on these documents in the past, but she cannot tell for sure. One thing that is certain is that she did not work on these documents on October 16th and 17th.

Let me know if we need to create a DevOps Bug to do some R&D in the next sprint to further investigate.

Thanks,
-Martin

Hi Harsh :

After posting this message, I did update IC/0308 last night, but I do not believe  IN/0131 and IC/0525 have been updated since then.

Thanks,

Paul

Hi Paul ,

I have checked in database and found both following Dispute have been updated on app.islg by Nafiseh user.

IN/0131 : Last Updated on 18th October
IC /0525 : Last Updated on 17th October

Nafiseh , Did you updated any thing on these disputes ?

Cc : Martin  

Hi Harsh ,

No, I did not update these two disputes on the specified dates. It should be Gary, as he is drafting DCDs (analyzing data capture) for IN/0131/01, and he also uploaded a new document under IC/0525 on October 17th.

Thanks,

Nafiseh

The problem seems to have spread to Dispute Document as well. As shown in the video below, the same time stamp applies to multiple dispute documents. 

Last Updated timestamp issue (20-Oct-22).mp4 3.08 MB • Download

The latest example from the beginning of the video to 0:32.

Last Updated timestamp issue 2 - UN-0041 claimant nationality - IC-0249 proceeding details (27-Oct-22).mp4 10.5 MB • Download

Issue: A Dispute Document has my name displayed as the person who last edited the document on app.islg.  However, I have not been in this document today.


Dispute Document UN/0332/03 shows that it was last updated by me today, October 31st at 12:35pm server time. 

image.png 12.8 KB • Download

And then again today, October 31st at 1:08pm server time.

image.png 35.7 KB • Download

I have not been in this document today on app.islg.  I did, however go in to BIT/0619 on app.islg at approximately those two times.  BIT/0619 is a Treaty that is referred to in UN/0332/03.  I don't know if this is what is causing this time stamp issue, but it's something to look into.

Thanks,
Irit

Hi Martin :

Unfortunately, this issue continues to be a concern.

On app.islg admin site, I am marked as the person who last updated IN/0157/01 today at 10:38 server time. However, I was not even online at 10:38 server time.

image.png 3.89 KB • Download

It is concerning that we cannot trust the time stamp. Is the server randomly registering someone when in fact the document is edited by somebody else?

Thanks,

Paul

Hi Paul , when did you last update this document? 
II wonder if the "last updated by" field is correct, but the "last updated date" is not. In other words, we might have an issue where the date field wrongly gets updated. We will investigate. 

Hi Martin :

I lasted updated the document on November 22nd, but Irit updated it after me on November 23rd based on document history. I have not updated anything since, as it is a published document.

Thanks,

Paul

Hi Piyush and Harsh ,

I have reopened https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/2205 and put it in our current sprint.

Thanks,
-Martin

Hi Paul and Martin ,

We got the issue. The issue is occured when any user create draft version. That time we copied last updated user from wrong place.

We update this thing in Stored procedure and uploaded on app.islg.

Please do monitor this thing in upcoming days and let us know if you still face this issue.

Thanks for the update, Harsh . I'll re-open it if we notice anything again.

Paul

This is a recurring error. Could you look into this?

Wrong person cited as last updated under dispute document (18-Jan-23).mp4 1.29 MB • Download

Thanks,

Paul

Hi Harsh ,

I have re-opened https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/2205 and inserted it in the current sprint. Can you investigate?

Thanks,
-Martin

Hi Paul   and Martin ,

We have again updated in same query. As per our knowledge when you created the draft version then we added Last updated by from previous document. Now we change in query. 

Now, Who will generate the draft version his/her name will be added in Last updated by column.

Let's monitoring closely for next one week. 

Hello Irit Séverine Gary :

When you create a draft or update of an existing dispute or dispute document, please see if your name correctly appears as the last updated person for the next week. When someone else's name incorrectly appears when you make an update, please create a video similar to what I've done above (you can record after the fact immediately after you notice) and post here.

Thank you,

Paul

I am marking this complete, as the new thread is started in https://3.basecamp.com/5523910/buckets/30650585/todos/5945511756#__subscriptions.