User friendly automation scheduling without cron#1150
Open
ClaireGz wants to merge 5 commits into
Open
Conversation
Replace the raw-cron-only escape hatch in the automation schedule trigger with friendly pickers: pick a frequency (hourly, daily, weekdays, weekly, monthly) and a time (HH:MM), day of week, or day of month, and the cron is generated under the hood. An "Advanced (cron)" option preserves raw cron input for power users, with a live human-readable description. Add cron-schedule helpers (build/parse/describe) with unit tests. Times are interpreted in the server timezone, consistent with existing backend behavior and the "server time" labels in the details sidebar. Closes #1130 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
🚀 Preview Deployment
Preview will be automatically removed when this PR is closed. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 3 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Move the frequency select inline right after the "On schedule" label so the granularity and its time/day inputs read left-to-right as a single phrase (e.g. "On schedule [Daily] at [09:00]"), with the delete icon pinned right. Frequency-specific controls flow inline via fragments in a wrapping flex row. Layout only; cron generation is unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Extend the friendly monthly day-of-month picker to cover all valid cron day-of-month values (1-31) and widen the build/parse clamps so schedules on the 29th-31st round-trip and stay in the friendly UI instead of falling back to Advanced. Strengthen the cron round-trip test to assert every relevant field per frequency and add a day-31 monthly case. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Weekly schedules now accept any combination of days via an inline toggle-button group (Mon-Sun), emitting a sorted comma-separated cron day list (e.g. 0 8 * * 1,3,5). Single-day and Sunday (0/7) still round-trip, and the explicit Weekdays 1-5 preset is preserved; at least one day stays selected so the day field is never empty. Hourly now uses a free numeric minute input (0-59) instead of a 5-minute select, so any minute round-trips. Extend cron-schedule tests: weekly multi-day and single-day round-trips, 1-5 vs comma-list mapping, and a non-multiple-of-5 hourly minute. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ClaireGz
changed the title
ClaireGz
changed the title
Bl3f
requested changes
Jul 15, 2026
Bl3f
left a comment
Bl3f
left a comment
Contributor
There was a problem hiding this comment.
Advanced mode visual is truncated. I also think we can remove the "Monthly on the 1st at 08:00" because when complex cron it writes "Custom schedule" which is useless and takes a row visually for nothing.
I'd also be in favour of putting space between the "On schedule" and the different inputs so it's aligned right like it was before.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Closes #1130
Implemented
Tests done