We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please make a clear and concise description of what the bug is.
Notes
User B gets notified about an updated file as notification. The same vice-versa.
User B is bombed with notifications as every change is transferred into a notification.
E.g. if user A is on shopping tour and just checking the todo list entries, this will trigger dozens of notifications for user B.
Please complete the following information.
I know this is dated and should be updates soon. Nevertheless, I have the same problem in other instances.
Nextcloud configuration:
Add relevant parts of your nextcloud.log and/or your browser's JavaScript console here.
nextcloud.log
The text was updated successfully, but these errors were encountered:
I tried to reproduce but #1375 blocks this somehow.
Sorry, something went wrong.
No branches or pull requests
Please make a clear and concise description of what the bug is.
Steps to reproduce
Notes
) from B to AExpected behaviour
User B gets notified about an updated file as notification. The same vice-versa.
Actual behaviour
User B is bombed with notifications as every change is transferred into a notification.
E.g. if user A is on shopping tour and just checking the todo list entries, this will trigger dozens of notifications for user B.
Server
Please complete the following information.
I know this is dated and should be updates soon. Nevertheless, I have the same problem in other instances.
Nextcloud configuration:
Client
Please complete the following information.
Log files
Add relevant parts of your
nextcloud.log
and/or your browser's JavaScript console here.The text was updated successfully, but these errors were encountered: