Skip to content

Folder and file share classification improvement #1217

@OlivierS1

Description

@OlivierS1

Actual behaviour

-Tell us what happens
When folders or files have the same name across accounts, and one or more of those files and folders are shared, the name of the folder of file will be have a "(N)" N being a number chosen by NC (incremental value it seems).
If I have a Document on one account and share it with another account, the name on the second account would be "Document (2)".
From the user who was given access to the share, it is not evident to say the share is from another account, nor from whom the share came from.
Under NC Dev 20170721, it doesn't even seem possible to know who provided the share.
For security and privacy reasons, and to prevent saving files in the wrong account, it would be really nice if the name of the file or folder containing the name of the person or group the share originated from. Instead of using the "(N)" designation, maybe "(username)" or for a group, the "Groupname".
To prevent such confusion with "Autoupload" default folder name, I usually add "_username" at the folder so I would get "Instantupload_username".
I find this approach makes sharing and receiving shares clearer to read and process.

Expected behaviour

-Tell us what should happen
Receiving a file or folder share, the name of the user or group should appear on the shared file or folder.

Steps to reproduce

Environment data

Android version:

Device model:

Stock or customized system:

Nextcloud app version:

Nextcloud server version:

Logs

Web server error log

Insert your webserver log here

Nextcloud log (data/nextcloud.log)

Insert your Nextcloud log here

NOTE: Be super sure to remove sensitive data like passwords, note that everybody can look here! You can use the Issue Template application to prefill some of the required information: https://apps.nextcloud.com/apps/issuetemplate

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions