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

[GH-ISSUE #2203] Adding Cron Parsing for Repeating Intervals #6593

New Issue
Open
opened 2026-04-20 17:11:29 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 17:11:29 -05:00
Owner
Copy Link

Originally created by @aileron565 on GitHub (Feb 8, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2203

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same feature request.

Description

By using adding cron format support for scheduling, it would greatly increase the flexibility of repeat intervals. This should be a fairly simple approach that already has go packages built to handle this use case would solve a large variety of scheduling situations and needs.

Which alternatives did you consider using instead?

No response

Originally created by @aileron565 on GitHub (Feb 8, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2203 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same feature request. ### Description By using adding cron format support for scheduling, it would greatly increase the flexibility of repeat intervals. This should be a fairly simple approach that already has go packages built to handle [this use case](https://github.com/adhocore/gronx?tab=readme-ov-file#next-tick) would solve a large variety of scheduling situations and needs. ### Which alternatives did you consider using instead? _No response_
GiteaMirror added the area/recurring-tasks label 2026-04-20 17:11:29 -05:00
GiteaMirror commented 2026-04-20 17:11:30 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 8, 2026):

Really unsure about this because cron is not very accessible to non-it people. And there is https://github.com/go-vikunja/vikunja/pull/2032 which will likely clash.

<!-- gh-comment-id:3866982986 --> @kolaente commented on GitHub (Feb 8, 2026): Really unsure about this because cron is not very accessible to non-it people. And there is https://github.com/go-vikunja/vikunja/pull/2032 which will likely clash.
GiteaMirror commented 2026-04-20 17:11:30 -05:00
Author
Owner
Copy Link

@aileron565 commented on GitHub (Feb 8, 2026):

That's a fair assessment. RRULEs are more traditionally used for calendar apps. I personally find RRULE strings to be harder to write and understand how all the pieces work together, but that might just be me.

I'm always an advocate to give users a few familiar choices, hence why I was suggesting as an alternative method instead of replacing the existing standard methods (whether that's the current implementation or RRULEs).

<!-- gh-comment-id:3868423343 --> @aileron565 commented on GitHub (Feb 8, 2026): That's a fair assessment. RRULEs are more traditionally used for calendar apps. I personally find RRULE strings to be harder to write and understand how all the pieces work together, but that might just be me. I'm always an advocate to give users a few familiar choices, hence why I was suggesting as an alternative method instead of replacing the existing standard methods (whether that's the current implementation or RRULEs).
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/recurring-tasks
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#6593
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?