nextcloud / nextcloud/flow_notifications
Notifications don't trigger for actions initiated by yourself
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 8
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 27
Description
I have set up a simple test case:
The NC Talk flow is just there to verify that I didn't misconfigure the conditions. When I edit/rename a file called test.md to test1.md (or vice versa), I get a message in Talk but no notification.
NC version: 20.0.4
Flow Notifications version: 1.0.3
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
No files, tests, or entry points are named. Start by reproducing the test.md to test1.md rename with Nextcloud 20.0.4 and Flow Notifications 1.0.3, then trace the notification action for self-initiated changes. Done means the rename produces a notification as well as the Talk message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100