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

[FEATURE REQUEST] Allow to go to the destination folder when the copy/move operation is finished #4379

Open
10 tasks
Aitorbp opened this issue Apr 10, 2024 · 4 comments

Comments

@Aitorbp
Copy link
Collaborator

Aitorbp commented Apr 10, 2024

Is your feature request related to a problem? Please describe.
Currently in the application, the operation of copying/moving a file when the operation is finished, the app keeps us in the source path and not in the destination path. There is nothing wrong with this, but I think usability would be improved if we at least gave the user the opportunity to choose whether to navigate to the source or the destination of the operation.

Describe the solution you'd like
As a first iteration I propose to open dialog when the copy/move operation is finished. Inside the dialog I would ask the users if they want to navigate to the destination folder where they have copied/moved the file.

Describe alternatives you've considered
Alternatively you could skip the dialog directly and redirect to the copied/moved folder.

TASKS

  • Research (if needed)
  • Create branch feature/allow_go_destination_folder_copy_move_operation
  • Development tasks
    • Implement whatever
    • ...
    • Implement unit tests (if needed)
  • Code review and apply changes requested
  • Design test plan
  • QA
  • Merge branch feature/feature_name into master
@jesmrec
Copy link
Collaborator

jesmrec commented Apr 10, 2024

My solution for this would be staying users in the folder they started to execute the action, i mean, where the copied/moved item was placed in first instance.

@JuancaG05
Copy link
Collaborator

Be careful with modal dialogs: they are a flaw for usability in most cases, they are too intrusive. They should be used for really necessary warnings (alerts) or for confirmation about an action the user performed. In this case, neither of the cases apply. If a user always wants to stay in the source folder and not in the destination one, you'll make them do one more click every time they do a copy/move operation. Not sure about this proposal.

Please, check behaviour with other similar apps (Google Drive, OneDrive, Dropbox...) to make a comparison.

@Aitorbp
Copy link
Collaborator Author

Aitorbp commented Apr 26, 2024

Behaviour similar apps:
Google Drive: the app keeps us in the source path (copy/move)
Box: the app keeps us in the source path (copy/move)
Google Files: the app keeps us in the source path (copy/move)
OneDrive: the app keeps us in the source path but the app gives us the possibility of going to the destination folder.
A Toast (or similar) appears indicating that the copy operation has worked (Something that we do not indicate when the operation is finished) and next to it a link to go to the destination folder.
Video about the behaviour:

onedrive_behaviour.mp4

@jesmrec
Copy link
Collaborator

jesmrec commented Apr 26, 2024

So, it's clear we should keep the current behaviour (stay in source folder), and adding an option in snackbar as enhancement. I'd add as Contributions are welcome in this one or other feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants