-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Add Bulk Tagging on new Files app [28+] #45935
Comments
I see no way to give a reaction to this (it simply isn't an option presented to me). However, bulk tagging ability is an important functionality of Nextcloud file management, and I believe it needs to be repaired and supported. |
I just added it. It should be good now. This is also an option that I would like to find again ! |
absolutely required feature ... |
I guess it is a regression from the migration to vue. Steps would be:
|
In which version will this be added again? |
How to use GitHub
Is your feature request related to a problem? Please describe.
Hello everyone,
Since my recent update to Nextcloud 28, I’ve noticed a change in the file tagging functionality. Previously, I had the ability to tag multiple files simultaneously, but this feature seems to have disappeared since the update. This limitation is causing an inconvenience as I frequently use the tagging feature to organize my files.
Describe the solution you'd like
I would like to have the ability to tag multiple files simultaneously reinstated in Nextcloud 28.
Describe alternatives you've considered
Currently, the only alternative is to tag files individually, which is time-consuming and less efficient.
Additional context
Has anyone else encountered this issue? Is it a new feature introduced in version 28, or is it potentially a bug? If anyone has information on this matter or has found a solution, I would appreciate it if you could share. Otherwise, can we consider reporting this as a potential issue to the development team?
Thank you in advance for your responses and assistance!
The text was updated successfully, but these errors were encountered: