Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OCIS-storage] overwriting a file as share receiver, does not create a new file version for the sharer #766

Closed
individual-it opened this issue Oct 28, 2020 · 3 comments
Assignees
Labels
Category:Defect Existing functionality is not working as expected QA:team Type:Bug

Comments

@individual-it
Copy link
Member

  1. share a file
  2. accept the share
  3. as share receiver overwrite the file
  4. as sharer check the versions of the file

current behaviour:
as sharer no versions are shown

maybe related to #763

@ScharfViktor
Copy link
Contributor

tested with local server oCIS version 1.11.0

current behaviour: receiver can overwrite file if file is located "Shares/Folder(with edit right)/file". receiver cannot add or overwrite a file to the folder "Shares"

as sharer can see new version of file. I suggest to close @individual-it

@individual-it
Copy link
Member Author

individual-it commented Sep 3, 2021

There is still a test that is marked as failing because of this issue https://github.com/owncloud/ocis/blob/master/tests/acceptance/expected-failures-API-on-OCIS-storage.md#ocis-storage-overwriting-a-file-as-share-receiver-does-not-create-a-new-file-version-for-the-sharer
we need to find out why that test still fails and tag it correctly, I suggest to keep this issue open for that

ToDo QA:team:

  • find out why apiVersions/fileVersionsSharingToShares.feature:32 still fails and tag it with the correct issue. If the problem is not this issue, close it

@dpakach dpakach self-assigned this Nov 16, 2021
@dpakach
Copy link
Contributor

dpakach commented Nov 16, 2021

ToDo QA:team:

  • find out why apiVersions/fileVersionsSharingToShares.feature:32 still fails and tag it with the correct issue. If the problem is not this issue, close it

as of now the issue breaking that scenario is #2706
So closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:Defect Existing functionality is not working as expected QA:team Type:Bug
Projects
None yet
Development

No branches or pull requests

4 participants