Notifications on changed notes are not superseeded
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 738
- Forks
- 162
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 35
Description
Please make a clear and concise description of what the bug is.
Steps to reproduce
- Have two users A and B with access to a NC instance
- Share a folder (e.g.
Notes) from B to A - On B's settings enable notifications via mail/feed on changes to notes/files.
- Create multiple change events using user A on some notes (multiple changes in the same note)
Expected 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.
- Notes app version: 4.5.1
- Nextcloud version: 23.0.3
- OS: Archlinux
- Web server: Apache as reverse proxy + apache
- PHP version: 8.0
- Database: mariadb 10.5.15
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.
- Browser (incl. version): Firefox 116.0.3 or Android app
- OS: Win/Linux/Android of various versions
Log files
Add relevant parts of your nextcloud.log and/or your browser's JavaScript console here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with two users, a shared folder, and multiple changes to the same note, then inspect how mail and feed notifications are generated. Done means repeated changes to one note are consolidated or superseded instead of producing a separate notification for every change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100