github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 19:47:47 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Deleted and unassigned user still received "task overdue" emails #2374

New Issue
Closed
opened 2026-03-22 14:04:51 -05:00 by GiteaMirror · 28 comments
GiteaMirror commented 2026-03-22 14:04:51 -05:00
Owner
Copy Link

Originally created by @bigbeka on GitHub (Oct 1, 2025).

Description

  1. Task was created with due date, user A was assigned.
  2. Task was reassigned to user B with overdue date
  3. User A was removed from the team and the User A still receives daily email notifications about overdue task that is not assigned to User A and User A doesn't have access to the task/team.

Vikunja Version

Version: v0.24.6

Browser and version

Safari latest

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @bigbeka on GitHub (Oct 1, 2025). ### Description 1. Task was created with due date, user A was assigned. 2. Task was reassigned to user B with overdue date 3. User A was removed from the team and the User A still receives daily email notifications about overdue task that is not assigned to User A and User A doesn't have access to the task/team. ### Vikunja Version Version: v0.24.6 ### Browser and version Safari latest ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 14:04:52 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 1, 2025):

Do you have the same problem with the latest RC or an unstable build?

@kolaente commented on GitHub (Oct 1, 2025): Do you have the same problem with the latest RC or an unstable build?
GiteaMirror commented 2026-03-22 14:04:53 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 1, 2025):

Sorry, I will try to reproduce this with the latest RC/unstable build. I am experiencing it on my production instance with the team.

@bigbeka commented on GitHub (Oct 1, 2025): Sorry, I will try to reproduce this with the latest RC/unstable build. I am experiencing it on my production instance with the team.
GiteaMirror commented 2026-03-22 14:04:53 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 3, 2025):

@kolaente concluded the test, and I can confirm that yes, this bug also happens on Version: v1.0.0-rc2-75-5f1d6845.

I will further run the test, by removing the user (Will) from the team, where the user will lose access to the task, and expected bug outcome is that Will receive reminder email during next reminder cycle.

User (Will) was unassigned from the task after the first reminder about overdue task. But remained in the team to which the user was originally a part of.

This morning, unassigned user received reminder notification email about the overdue task.

Image Image
@bigbeka commented on GitHub (Oct 3, 2025): @kolaente concluded the test, and I can confirm that yes, this bug also happens on Version: `v1.0.0-rc2-75-5f1d6845`. I will further run the test, by removing the user (Will) from the team, where the user will lose access to the task, and expected bug outcome is that Will receive reminder email during next reminder cycle. User (Will) was unassigned from the task after the first reminder about overdue task. But remained in the team to which the user was originally a part of. This morning, unassigned user received reminder notification email about the overdue task. <img width="893" height="848" alt="Image" src="https://github.com/user-attachments/assets/9333f070-fdb3-46b3-8c65-43c144cc8dff" /> <img width="588" height="469" alt="Image" src="https://github.com/user-attachments/assets/19c689dd-db93-44ae-a0e5-79d6d0bab39e" />
GiteaMirror commented 2026-03-22 14:04:54 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 4, 2025):

@kolaente I concluded the test and was able to reproduce the bug on v1.0.0-rc2-75-5f1d6845. The team member who had a task assigned to them kept receiving "task overdue" notifications after the task was reassigned to admin, and the notifications are continuing even after the member was removed from the team (this user doesn't have access to any shared projects).

@bigbeka commented on GitHub (Oct 4, 2025): @kolaente I concluded the test and was able to reproduce the bug on `v1.0.0-rc2-75-5f1d6845`. The team member who had a task assigned to them kept receiving "task overdue" notifications after the task was reassigned to admin, and the notifications are continuing even after the member was removed from the team (this user doesn't have access to any shared projects).
GiteaMirror commented 2026-03-22 14:04:54 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 8, 2025):

Draft PR with a fix is up on https://github.com/go-vikunja/vikunja/pull/1620

@kolaente commented on GitHub (Oct 8, 2025): Draft PR with a fix is up on https://github.com/go-vikunja/vikunja/pull/1620
GiteaMirror commented 2026-03-22 14:04:55 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 8, 2025):

Will wait for the next stable release.

@bigbeka commented on GitHub (Oct 8, 2025): Will wait for the next stable release.
GiteaMirror commented 2026-03-22 14:04:55 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 8, 2025):

Well the PR is not even merged...

@kolaente commented on GitHub (Oct 8, 2025): Well the PR is not even merged...
GiteaMirror commented 2026-03-22 14:04:56 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 9, 2025):

Haha, yes I have been waiting for over a year for the next stable release with many bug fixes. Its good to see there are already candidates for v1.0.0.

@bigbeka commented on GitHub (Oct 9, 2025): Haha, yes I have been waiting for over a year for the next stable release with many bug fixes. Its good to see there are already candidates for v1.0.0.
GiteaMirror commented 2026-03-22 14:04:57 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 9, 2025):

The PR is now merged, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Oct 9, 2025): The PR is now merged, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-03-22 14:04:57 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 9, 2025):

I will report back with unstable version testing.

@bigbeka commented on GitHub (Oct 9, 2025): I will report back with unstable version testing.
GiteaMirror commented 2026-03-22 14:04:57 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 15, 2025):

@kolaente results are in (Version: v1.0.0-rc2-135-7689b6c1). Now, the user (Will) who was assigned to the task didn't receive reminder notification at all, instead the admin (Beck) who created the task received the notification while the task was assigned to the user 'Will'.

Admin received the reminder about overdue task after 24 hours of waiting while the task was assigned to admin.

Just a recap, user Will is part of a team, a parent project is shared with that team. So the user has access to the task via the team.

Read the emails top > bottom

Image
@bigbeka commented on GitHub (Oct 15, 2025): @kolaente results are in (`Version: v1.0.0-rc2-135-7689b6c1`). Now, the user (`Will`) who was assigned to the task didn't receive reminder notification **at all**, instead the admin (`Beck`) who created the task received the notification **while** the task was assigned to the user 'Will'. Admin received the reminder about overdue task after 24 hours of waiting while the task was assigned to admin. Just a recap, user `Will` is part of a team, a parent project is shared with that team. So the user has access to the task via the team. Read the emails top > bottom <img width="2141" height="1142" alt="Image" src="https://github.com/user-attachments/assets/bc43d11d-c6f5-4b2d-af54-4072d41a3cfb" />
GiteaMirror commented 2026-03-22 14:04:59 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 19, 2025):

Do you see the same problem when the project the task is in is directly shared? (not a sub project)

@kolaente commented on GitHub (Oct 19, 2025): Do you see the same problem when the project the task is in is directly shared? (not a sub project)
GiteaMirror commented 2026-03-22 14:04:59 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 19, 2025):

I will test this, I have created a new user on the same test instance Version: v1.0.0-rc2-135-7689b6c1 and admin (task/project owner) user shared the parent project (that I created for previous test) with the user ben and assigned 1 overdue task from previous task and also create a fresh task in the same project and assigned it to ben and set the due date. Will see how tomorrow's emails will come in for ben@fqdn.io and the admin inbox.

Another bug?: Funny side effect that "popped up": Even though the Test123 task that was already overdue and unassigned from user will after last test and reassigned to owner user and now assigned to user ben still gets "Test123" (#1) has been assigned to ben email. - So just to recap on this: Task Test123 was created by project owner, user Will was shared access to the project and then the task Test123 was assigned to Will. After reassigning task Test123 back to owner, Will didn't get any overdue task email notifications, but when owner of the task reassigned the task from owner to Ben, user Will which has access to the project gets a "Test123" (#1) has been assigned to ben notifications. I believe user Will should not get any notifications about admin reassigning tasks to another user. Or is it a feature?

@bigbeka commented on GitHub (Oct 19, 2025): I will test this, I have created a new user on the same test instance `Version: v1.0.0-rc2-135-7689b6c1` and admin (task/project owner) user shared the parent project (that I created for previous test) with the user `ben` and assigned 1 overdue task from previous task and also create a fresh task in the same project and assigned it to `ben` and set the due date. Will see how tomorrow's emails will come in for ben@fqdn.io and the admin inbox. **Another bug?**: Funny side effect that "popped up": Even though the `Test123` task that was already overdue and unassigned from user `will` after last test and reassigned to owner user and now assigned to user `ben` still gets `"Test123" (#1) has been assigned to ben` email. - So just to recap on this: Task `Test123` was created by project owner, user `Will` was shared access to the project and then the task `Test123` was assigned to `Will`. After reassigning task `Test123` back to owner, `Will` didn't get any overdue task email notifications, but when owner of the task reassigned the task from owner to `Ben`, user `Will` which has access to the project gets a `"Test123" (#1) has been assigned to ben` notifications. I believe user `Will` should not get any notifications about admin reassigning tasks to another user. Or is it a feature?
GiteaMirror commented 2026-03-22 14:04:59 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 19, 2025):

I believe user Will should not get any notifications about admin reassigning tasks to another user. Or is it a feature?

This is a feature, when you assign a user they are subscribed, which can also be done manually and will result in notifications getting sent out about these kinds of events.

@kolaente commented on GitHub (Oct 19, 2025): > I believe user Will should not get any notifications about admin reassigning tasks to another user. Or is it a feature? This is a feature, when you assign a user they are subscribed, which can also be done manually and will result in notifications getting sent out about these kinds of events.
GiteaMirror commented 2026-03-22 14:05:00 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 19, 2025):

Cool, I unsubscribed user Will from all the tasks. I will report back about user Ben who has access to the project directly and has 2 tasks assigned.

@bigbeka commented on GitHub (Oct 19, 2025): Cool, I unsubscribed user `Will` from all the tasks. I will report back about user `Ben` who has access to the project directly and has 2 tasks assigned.
GiteaMirror commented 2026-03-22 14:05:00 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Oct 20, 2025):

@kolaente so the reminder emails were triggered this morning, now the user Ben who has direct share (read/write) access to the project did not receive any notification (either for old task that was originally assigned to user Will or the new task that was created and assigned to user Ben yesterday). As user Ben is assigned to both tasks, this user is also subscribed to both task notifications.

The owner/admin user beck of the project and the two tasks received "Your overdue tasks" notification as that user is subscribed to both of them.

@bigbeka commented on GitHub (Oct 20, 2025): @kolaente so the reminder emails were triggered this morning, now the user `Ben` who has direct share (read/write) access to the project **did not** receive any notification (either for old task that was originally assigned to user `Will` or the new task that was created and assigned to user `Ben` yesterday). As user `Ben` is assigned to both tasks, this user is also subscribed to both task notifications. The owner/admin user `beck` of the project and the two tasks received "Your overdue tasks" notification as that user is subscribed to both of them.
GiteaMirror commented 2026-03-22 14:05:00 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 16, 2025):

Took me a while to get back to this, sorry about that.

If you're logged in as Ben, does it show the task as subscribed in the frontend?

@kolaente commented on GitHub (Nov 16, 2025): Took me a while to get back to this, sorry about that. If you're logged in as `Ben`, does it show the task as subscribed in the frontend?
GiteaMirror commented 2026-03-22 14:05:01 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Nov 16, 2025):

No problem at all. I kept the dev environment, so I just restarted it. User Ben is subscribed to both tasks. Please see my last comment. As I said, User Ben did not receive any notification about overdue tasks after being assigned to the tasks (either while having access to the project via Teams or directly).

@bigbeka commented on GitHub (Nov 16, 2025): No problem at all. I kept the dev environment, so I just restarted it. User `Ben` is subscribed to both tasks. Please see my last comment. As I said, User `Ben` did not receive any notification about overdue tasks after being assigned to the tasks (either while having access to the project via Teams or directly).
GiteaMirror commented 2026-03-22 14:05:02 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Nov 17, 2025):

Kept the dev environment on, and this morning, admin (user Beck) received Your overdue tasks email with the two overdoes tasks, but user Ben who has access to the project where the tasks are and Ben is subscribed to both tasks.

As a sanity check, I did request a password reset link for Ben and successfully received the email, so SMTP and SPAM are not the problem.

@bigbeka commented on GitHub (Nov 17, 2025): Kept the dev environment on, and this morning, admin (user `Beck`) received `Your overdue tasks` email with the two overdoes tasks, but user `Ben` who has access to the project where the tasks are and `Ben` is subscribed to both tasks. As a sanity check, I did request a password reset link for `Ben` and successfully received the email, so SMTP and SPAM are not the problem.
GiteaMirror commented 2026-03-22 14:05:02 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 18, 2025):

Okay, so the original issue, where a user would receive task overdue mails for tasks in a project they no longer have access to is gone, but now users who are assigned to a task don't receive these mails?

@kolaente commented on GitHub (Nov 18, 2025): Okay, so the original issue, where a user would receive task overdue mails for tasks in a project they no longer have access to is gone, but now users who are assigned to a task don't receive these mails?
GiteaMirror commented 2026-03-22 14:05:02 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Nov 18, 2025):

Yes, that is correct. User Ben is assigned and Subscribed to 2 tasks in a project that is directly shared with Ben. Both tasks are 1 month overdue, and Ben doesn't receive overdue emails.

@bigbeka commented on GitHub (Nov 18, 2025): Yes, that is correct. User `Ben` is assigned and Subscribed to 2 tasks in a project that is directly shared with Ben. Both tasks are 1 month overdue, and Ben doesn't receive overdue emails.
GiteaMirror commented 2026-03-22 14:05:02 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 27, 2025):

I've tried to verify this and it seems to work as expected. Just to verify: Ben has enabled overdue task reminder mails in the user settings?

@kolaente commented on GitHub (Nov 27, 2025): I've tried to verify this and it seems to work as expected. Just to verify: `Ben` has enabled overdue task reminder mails in the user settings?
GiteaMirror commented 2026-03-22 14:05:03 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Nov 27, 2025):

I am very excited for the next stable release🤩 I was just checking the 3 RCs before you commented! Thank you for all your hard work @kolaente!

Yes, all test users mentioned above have default settings. Send me a summary of my undone overdue tasks every day is enabled for Ben as well, see here:

Image

One of the tasks assigned to Ben (created in a project by admin Beck and Ben has r/w access directly to the project, not via Teams):

Image

I pulled down the most recent unstable version for my testing environment just now (Version: v1.0.0-rc2-397-4de49512). I will keep the testing LXC going for tomorrow to see if the overdue reminder email start coming in for user Ben. Admin, who created these tasks received reminder emails consistently.

I believe rc3 is still building, once done, I will try that out too.

@bigbeka commented on GitHub (Nov 27, 2025): I am very excited for the next stable release🤩 I was just checking the 3 RCs before you commented! Thank you for all your hard work @kolaente! Yes, all test users mentioned above have default settings. `Send me a summary of my undone overdue tasks every day` is enabled for Ben as well, see here: <img width="1097" height="1080" alt="Image" src="https://github.com/user-attachments/assets/35033fad-1ecb-4554-a783-0a829021219d" /> ### One of the tasks assigned to Ben (created in a project by admin `Beck` and Ben has r/w access directly to the project, not via `Teams`): <img width="915" height="1214" alt="Image" src="https://github.com/user-attachments/assets/02c2663d-e31e-4f97-85d6-e521923dcc83" /> I pulled down the most recent `unstable` version for my testing environment just now (`Version: v1.0.0-rc2-397-4de49512`). I will keep the testing LXC going for tomorrow to see if the overdue reminder email start coming in for user `Ben`. Admin, who created these tasks received reminder emails consistently. I believe `rc3` is still building, once done, I will try that out too.
GiteaMirror commented 2026-03-22 14:05:03 -05:00
Author
Owner
Copy Link

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

New PR with a fix: https://github.com/go-vikunja/vikunja/pull/1901

It seems like the fix is straight forward: We were only checking if a user has read access on the project, not if they have read, write or admin access (all of these allow reading the task).

@kolaente commented on GitHub (Nov 28, 2025): New PR with a fix: https://github.com/go-vikunja/vikunja/pull/1901 It seems like the fix is straight forward: We were only checking if a user has read access on the project, not if they have read, write or admin access (all of these allow reading the task).
GiteaMirror commented 2026-03-22 14:05:03 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Nov 28, 2025):

This issue has been fixed in #1901, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Nov 28, 2025): This issue has been fixed in #1901, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
GiteaMirror commented 2026-03-22 14:05:04 -05:00
Author
Owner
Copy Link

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

Here we go again - please check with the next unstable build!

@kolaente commented on GitHub (Nov 28, 2025): Here we go again - please check with the next unstable build!
GiteaMirror commented 2026-03-22 14:05:04 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Nov 28, 2025):

I pulled down the latest Version: v1.0.0-rc3-4-7f5a08b3 now. I will see if tomorrow the notification for user Ben will start working. Thank you.

@bigbeka commented on GitHub (Nov 28, 2025): I pulled down the latest `Version: v1.0.0-rc3-4-7f5a08b3` now. I will see if tomorrow the notification for user `Ben` will start working. Thank you.
GiteaMirror commented 2026-03-22 14:05:05 -05:00
Author
Owner
Copy Link

@bigbeka commented on GitHub (Nov 29, 2025):

I confirm, the issue has been resolved in Version: v1.0.0-rc3-4-7f5a08b3. Many thanks!

@bigbeka commented on GitHub (Nov 29, 2025): I confirm, the issue has been resolved in `Version: v1.0.0-rc3-4-7f5a08b3`. Many thanks!
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#2374
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?