-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug]: Multiple bugs concerning tags #51233
Comments
point 2 sounds contra intuitive as the reason for collaborative tags is to be collaborative meaning multiple users can work with. So similar to github I expect the tags to be shares "use the red tag" should also be the red tag on that other users account. |
I'm aware of this collaborative aspect if tags... but, in real life, with large to very large Nextcloud instances, I can actually bet that there will be issues because there will always be a part of users that we can't obviously trust to take the right decisions : they will change color even if it's forbidden (which will create confusion for users who took their habits with old colors), or create unrelevant / inconsistent tags ... In large organizations, it's not possible to trust everyone in this context. This leads me to suggest another thing ; 3 user levels :
|
If tag creation is restricted to admin yes. Otherwise users should share the colors IMHO. |
We have different opinions on this 🙂 I think that on large instances, if everyone starts messing with the colors, the labels will change color regularly like Christmas tree lights, and it will be the same mess with the names. This is even more of a problem if the label was created by an administrator. There is no reason or logic for users to be able to change the color. In the case of labels managed by administrators, the colors should only be manageable by administrators. We have to take into account that labels are part of processes, such as helping to organize and qualify files, and that all this is often documented within organizations. So, we cannot allow users to touch labels created by administrators. If people do what they want, it must be understood that people who do not have the context, or are not rigorous, or do not have an overview to determine whether or not the creation or modification of a label is relevant, it will one day or another necessarily be a mess (e.g.: useless labels because redundant which will disturb other people who will confuse them; this could cause poorly labeled files to escape certain automated flows). In other words, apart from administrators (and delegated administrators that I propose to add), labels must be strictly personal (even if you add a parameter to allow the 2 behaviors for normal users: collaborative or individual labels). I would like to broaden the discussion to other people to see things can be changed in the sense of what I describe. @jancborchardt @nickvergessen @skjnldsv ? or others ? |
I think it makes sense to limit coloring to the user creating the label or the admin. |
There could be plenty reasons to do so, especially if you do not have a structure like "admin setup everything" but smaller work groups where people create and organize things in their teams.
If there is a special "admin label" then yes fully agree with you |
Bug description
Steps to reproduce
Check bug description above
Expected behavior
Check bug description above
Nextcloud Server version
31
Operating system
RHEL/CentOS
PHP engine version
PHP 8.2
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 32.0.1 to 32.0.2)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Can be provided if necessary
The text was updated successfully, but these errors were encountered: