Skip to content

Let users know that cron schedule is UTC - #5248

Open
taylordowns2000 wants to merge 1 commit into
mainfrom
cron-is-utc
Open

taylordowns2000 wants to merge 1 commit into
mainfrom
cron-is-utc

Conversation

@taylordowns2000

Copy link
Copy Markdown
Member

Adds a small "All times in UTC" note to the cron trigger's edit step and read-only panel, since schedules always run in UTC but the UI never said so. It reuses the panels' existing muted hint style, and adds an optional hint prop to ReadOnlyField to show it there. Closes #5247.

Validation steps

  1. Open the cron scheduler panel and check it out! 👀

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

  • I have used Claude Code
  • I have used another model
  • I have not used AI

You can read more details in our
Responsible AI Policy

Pre-submission checklist

  • I have performed an AI review of my code (we recommend using /review
    with Claude Code)
  • I have implemented and tested all related authorization policies.
    (e.g., :owner, :admin, :editor, :viewer)
  • I have updated the changelog.
  • I have ticked a box in "AI usage" in this PR

@github-project-automation github-project-automation Bot moved this to New Issues in Core Oct 14, 2026
@taylordowns2000 taylordowns2000 changed the title fix #5247 Let users know that cron schedule is UTC Oct 14, 2026
@github-actions

Copy link
Copy Markdown

Security Review ✅

  • S0 (project scoping): N/A, this is a frontend-only UI change adding a "All times in UTC" label to cron trigger panels — no queries, data access, or project-scoped resources are touched.
  • S1 (authorization): N/A, no new web-layer actions, controllers, LiveView events, or policy modifications; only presentational React components changed.
  • S2 (audit trail): N/A, no mutations or writes to project/instance configuration resources — the diff is purely a cosmetic hint on display components.

@taylordowns2000

Copy link
Copy Markdown
Member Author

@lmac-1 , @elias-ba , the HEX warning (lint failure) is unrelated to this branch.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New Issues

Development

Successfully merging this pull request may close these issues.

Users can't know when they've schedule their workflows to run

1 participant