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

Sync Protocol fails to mention source name when renaming a file #9238

Closed
jnweiger opened this issue Nov 23, 2021 · 2 comments
Closed

Sync Protocol fails to mention source name when renaming a file #9238

jnweiger opened this issue Nov 23, 2021 · 2 comments
Assignees
Labels
p2-high Escalation, on top of current planning, release blocker
Milestone

Comments

@jnweiger
Copy link
Contributor

jnweiger commented Nov 23, 2021

Seen in 2.9.2-rc5

  • connect to demo.owncloud.org

  • wait for the initial sync to succeed

  • visit the Photos folder with a local file browser, rename one of the photos to foo.jpg

  • after the next sync run, the Sync Protocol tab has
    image

  • The user cannot tell, what the old name of the photo was. BAD

  • The new name of the file is shown twice. That is redundant.

Expected behaviour:

  • For a move, report both, old and new name. E.g.
    • Action: Moved from Photos/Portugal.jpg
    • File: Photos/foo.jpg
@github-actions
Copy link

This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Dec 24, 2021
@github-actions
Copy link

The issue was marked as stale for 7 days and closed automatically.

@TheOneRing TheOneRing removed the Stale label Jan 4, 2022
@TheOneRing TheOneRing added this to the 2.10 milestone Jan 4, 2022
@TheOneRing TheOneRing reopened this Jan 4, 2022
@TheOneRing TheOneRing modified the milestones: 2.10, 2.10.1 Feb 14, 2022
@TheOneRing TheOneRing added the p2-high Escalation, on top of current planning, release blocker label Feb 14, 2022
@erikjv erikjv self-assigned this Feb 17, 2022
@TheOneRing TheOneRing mentioned this issue Mar 10, 2022
55 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

No branches or pull requests

3 participants