Incorrect user name in version history list

[fuzi1996]

Do you want to request a feature or report a bug?

I think it's a bug

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

I use the java-spring code in this repository document-server-intergration

follow the steps to reproduce:

1. John Smith uploaded a new file

2. John Smith opened the file

3. Mark Pottato opened the same file

4. John Smith wrote his name

5. Mark Pottato wrote his name

6. John Smith closed edit window

7. Mark Pottato closed edit window

The history data was

{
	"history": [
		{
			"created": "2022-05-30 19:33:17",
			"version": 1,
			"user": {
				"name": "John Smith",
				"id": "1"
			},
			"key": "-277263181"
		},
		{
			"serverVersion": "7.0.1",
			"created": "2022-05-30 11:35:00",
			"changes": [
				{
					"created": "2022-05-30 11:35:00",
					"user": {
						"name": "John Smith",
						"id": "1"
					}
				},
				{
					"created": "2022-05-30 11:35:33",
					"user": {
                                                // should display this user name
						"name": "group-2 Mark Pottato",
						"id": "2"
					}
				}
			],
			"version": 2,
			"user": {
                                // display name seem like was this value,not the newest one in changes
				"name": "John Smith",
				"id": "1"
			},
			"key": "-222804329"
		}
	],
	"currentVersion": 2
}

The store content in changes.json file was:

{
	"serverVersion": "7.0.1",
	"changes": [
		{
			"created": "2022-05-30 11:35:00",
			"user": {
				"id": "1",
				"name": "John Smith"
			}
		},
		{
			"created": "2022-05-30 11:35:33",
			"user": {
				"id": "2",
				"name": "group-2 Mark Pottato"
			}
		}
	]
}

What is the expected behavior?

Did this work in previous versions of DocumentServer?

No

DocumentServer version:

Operating System:

Windows 11

Browser version:

[ShockwaveNN]

Hi, not sure that we got enought free time to localize this problem if it occurs in Java spring example, but could you check out our default nodejs example with your scenario and see if same problem can be reproduced?

[fuzi1996]

I try to reproduced it, the follow is the env:

documentserver: onlyoffice/documentserver:7.1.1.23
node-js-example:  the newest version(hash:05a3110c99423dafd24b6edbdda77678548c9a4d)

unfortunately, it was reproduced, so I think it must a bug

[ShockwaveNN]

@fuzi1996 Thanks for explanation, seems something wrong, we'll take a closer look at this issue

[matveevms]

Hello, @fuzi1996 Thank you for the report. I created new issue 57575 in our private issue tracker.