github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-15 22:32:29 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #1170] Assigned user does not receive notification when another project member is subscribed #6330

New Issue
Closed
opened 2026-04-20 16:54:54 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-20 16:54:54 -05:00
Owner
Copy Link

Originally created by @mnadalin on GitHub (Jul 24, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1170

Description

When a task is created and assigned to a user, that user should be notified. However, if another project member is subscribed to the project, the actual assignee does not receive any notification — and only the subscribed user is notified.

Steps to reproduce

  1. Create a project Azkaban, owned by Administrator.

  2. Share the project with two users:

    • Harry Potter: Read/Write
    • Voldemort: Read/Write

  3. As Voldemort, create a new task and assign it to Administrator.
    ✅ Administrator receives the "You have been assigned to the task" notification.

  4. Now, Harry Potter subscribes to the project Azkaban.

  5. Again, as Voldemort, create another task and assign it to Administrator.
    ❌ Administrator receives no notification.
    ✅ Harry Potter receives a notification, even though he is not involved in the task.

The same problem occurs when using APIs:

  1. Voldemort logs in with username and password using /api/v1/login
  2. Voldemort create a new task using /api/v1/projects/<PROJECT_ID>/tasks
  3. Voldemort assign the new task to Administrator using /api/v1/tasks/<TASK_ID>/assignees

Vikunja Version

Cloned yesterday from commit 97a7e40

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @mnadalin on GitHub (Jul 24, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1170 ### Description When a task is created and assigned to a user, that user should be notified. However, if another project member is subscribed to the project, the actual assignee **does not receive any notification** — and only the subscribed user is notified. --- ### Steps to reproduce 1. Create a project `Azkaban`, owned by `Administrator`. 2. Share the project with two users: * `Harry Potter`: Read/Write * `Voldemort`: Read/Write 3. As `Voldemort`, create a new task and assign it to `Administrator`. ✅ `Administrator` receives the "You have been assigned to the task" notification. 4. Now, **Harry Potter subscribes to the project `Azkaban`**. 5. Again, as `Voldemort`, create another task and assign it to `Administrator`. ❌ `Administrator` receives **no notification**. ✅ `Harry Potter` receives a notification, even though he is not involved in the task. --- The same problem occurs when using APIs: 1. Voldemort logs in with username and password using `/api/v1/login` 2. Voldemort create a new task using `/api/v1/projects/<PROJECT_ID>/tasks` 3. Voldemort assign the new task to Administrator using `/api/v1/tasks/<TASK_ID>/assignees` ### Vikunja Version Cloned yesterday from commit 97a7e40 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:54:55 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 24, 2025):

Did you verify if it works on the demo?

<!-- gh-comment-id:3113539536 --> @kolaente commented on GitHub (Jul 24, 2025): Did you verify if it works on the demo?
GiteaMirror commented 2026-04-20 16:54:56 -05:00
Author
Owner
Copy Link

@mnadalin commented on GitHub (Jul 24, 2025):

Did you verify if it works on the demo?

Three users are needed to reproduce.

<!-- gh-comment-id:3113561216 --> @mnadalin commented on GitHub (Jul 24, 2025): > Did you verify if it works on the demo? Three users are needed to reproduce.
GiteaMirror commented 2026-04-20 16:54:56 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 24, 2025):

You can register new users on the demo.

<!-- gh-comment-id:3113586463 --> @kolaente commented on GitHub (Jul 24, 2025): You can register new users on the demo.
GiteaMirror commented 2026-04-20 16:54:56 -05:00
Author
Owner
Copy Link

@mnadalin commented on GitHub (Jul 24, 2025):

My bad, thought it was only demo / demo.
Yes, just tried. I can reproduce the problem on try.vikunja.it

<!-- gh-comment-id:3114795807 --> @mnadalin commented on GitHub (Jul 24, 2025): My bad, thought it was only demo / demo. Yes, just tried. I can reproduce the problem on try.vikunja.it
GiteaMirror commented 2026-04-20 16:54:57 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 28, 2025):

There was a similar issue https://github.com/go-vikunja/vikunja/issues/1181 which has been fixed. Can you still verify this with the latest unstable build or on the demo?

<!-- gh-comment-id:3126311068 --> @kolaente commented on GitHub (Jul 28, 2025): There was a similar issue https://github.com/go-vikunja/vikunja/issues/1181 which has been fixed. Can you still verify this with the latest unstable build or on the demo?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6330
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?