nextcloud / nextcloud/deck

Notifications on an assigned user

Open
#3,547 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: activity feature: notification feature: sharing question
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

We are testing Deck to replace a very popular issue tracker in our organization.
NC v22.2.3, Deck v1.5.5 .

I'm unable to find the documentation on the deck notifications configuration but for what I've seen, in a shared board notifications are sent to all the users that (by means of either direct or group membership) can access to that board.
Since we don't need such a pervasive notification behaviour, we have disabled the 3 notifications flags that are related to Deck in NC settings.

By doing so I found that (as I hoped) assigments are still notified to the assignee. But, changes to assigned cards are not notified as well.

Example: Bob is the reporter of an issue, John is the assignee working on that. We set both in the Assignee field and we would expect they are notified of any change to that issue, while the rest of the group is notified according to the each user's notifications settings.

To wrap up: It would be great to notify a user for all the changes to a card where he/she is in the Assignees of that card (possibiy making it configurable).

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing Deck's notification configuration and the handling of changes to assigned cards. Check how assignment notifications differ from change notifications, then verify that an assigned user receives relevant card updates without notifying every board member, including whether this behavior can be configured.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.