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

[GH-ISSUE #1841] Auto adding reminder to new tasks based on project settings #6491

New Issue
Closed
opened 2026-04-20 17:05:39 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-20 17:05:39 -05:00
Owner
Copy Link

Originally created by @belidzs on GitHub (Nov 18, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1841

Description

I'd like to implement this feature someone has requested (which I could use as well): https://community.vikunja.io/t/auto-reminder-setting/604

Is it OK if I go ahead?

Which alternatives did you consider using instead?

No response

Originally created by @belidzs on GitHub (Nov 18, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1841 ### Description I'd like to implement this feature someone has requested (which I could use as well): https://community.vikunja.io/t/auto-reminder-setting/604 Is it OK if I go ahead? ### Which alternatives did you consider using instead? _No response_
GiteaMirror added the area/remindersarea/projects labels 2026-04-20 17:05:39 -05:00
GiteaMirror commented 2026-04-20 17:05:41 -05:00
Author
Owner
Copy Link

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

Sounds great!

I think this should be a frontend-only feature since it's a little magic - when integrating with the api that should be predictable and not behave differently depending on what the user has configured in their settings.

A few notes on the implementation:

  • This should be stored in the frontend only - as a frontend setting saved with the user
  • Configuring this should go to user settings
<!-- gh-comment-id:3546422907 --> @kolaente commented on GitHub (Nov 18, 2025): Sounds great! I think this should be a frontend-only feature since it's a little magic - when integrating with the api that should be predictable and not behave differently depending on what the user has configured in their settings. A few notes on the implementation: - This should be stored in the frontend only - as a frontend setting saved with the user - Configuring this should go to user settings
GiteaMirror commented 2026-04-20 17:05:41 -05:00
Author
Owner
Copy Link

@belidzs commented on GitHub (Nov 22, 2025):

Thanks for the clarification, it's very useful.

My original plan was to implement this in the API layer so that the automation triggers regardless of the calling client. Good thing I asked first. As I'm not an expert in frontend technologies, I better leave this to someone else instead.

<!-- gh-comment-id:3565951020 --> @belidzs commented on GitHub (Nov 22, 2025): Thanks for the clarification, it's very useful. My original plan was to implement this in the API layer so that the automation triggers regardless of the calling client. Good thing I asked first. As I'm not an expert in frontend technologies, I better leave this to someone else instead.
GiteaMirror commented 2026-04-20 17:05:43 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Apr 11, 2026):

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

<!-- gh-comment-id:4230252831 --> @vikunja-bot-app[bot] commented on GitHub (Apr 11, 2026): This issue has been fixed in #2607, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
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 area/projects area/reminders
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#6491
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?