folder name not rename for sharee when sharer rename the folder

[nabim777]

Describe the bug

When sharer renamed the share folder then the folder name is not renamed for sharee. Due to this, there is also difficult to search for sharee to search the folder by name

Steps to reproduce

Steps to reproduce the behavior:

1. As marie, create a folder folder1
2. As marie, share a folder to einstein
3. As einstein, accept the share
4. As marie, rename folder folder1 to folder2

Expected behavior

The folder should be renamed

for sharer marie

for sharee einstein

Actual behavior

The folder is not renamed for sharee

for sharer marie

for sharee einstein

[phil-davis]

The screen shots show folders called folders and folder, but the test description of the steps to reproduce has folder and folder1 - that makes it confusing to understand the issue.

Also, the Actual Behavior section has the text "The response contains resource named folder in the response"
IMO it should say "The response does not contain resource named folder in the response"

[nabim777]

The screen shots show folders called folders and folder, but the test description of the steps to reproduce has folder and folder1 - that makes it confusing to understand the issue.

Also, the Actual Behavior section has the text "The response contains resource named folder in the response" IMO it should say "The response does not contain resource named folder in the response"

oh sorry for that mistake. I've updated

[saw-jan]

AFAIK, the behavior where the resource (accepted share) doesn't get renamed in the sharee side is expected.

CC @ScharfViktor

[phil-davis]

Now the issue describes what is known expected behavior. When a sharer renames a resource, a sharee who has already received the resource still sees it with its original name. This is the way "the system" is expected to work. A sharee can also rename a received resource, and the sharee is the only user that sees the changed name.

I think that this issue is supposed to be about searching?

[ScharfViktor]

the behavior is expected. same issue #6376

[saw-jan]

Then I will close this here. @nabim777 open another issue that is related to REPORT

[nabim777]

Then I will close this here. @nabim777 open another issue that is related to REPORT

Here is related to REPORT #7262