feat(automations): rename Scheduled Tasks UI to Automations (UI only) - #3260
Merged
rahulrav1 merged 5 commits intoJul 25, 2026
Merged
Conversation
…copy only) UI-facing name is now 'Automations'; internal name (DB/CRUD/API/components/ comments/route) remains 'scheduled task'. Changes limited to user-visible display strings in 5 source files + 2 test files. Changed: - TasksPage.tsx: h1, search placeholder, load error, loading text, empty states - Sidebar.tsx: nav label "Scheduled" → "Automations" - CommandPalette.tsx: "Go to Scheduled tasks" → "Go to Automations" - CreateScheduledTaskDialog.tsx: dialog titles + error messages - Test assertions updated to match new copy No component names, file names, types, data-testids, routes, or backend paths were altered. Signed-off-by: Rahul Ravindranathan <rahulnathan73@gmail.com>
rahulrav1
force-pushed
the
OMNI-1193-rename-automations-ui
branch
from
July 25, 2026 01:50
34c1d74 to
bd7980a
Compare
Signed-off-by: Rahul Ravindranathan <rahulnathan73@gmail.com>
…nternal) naming Signed-off-by: Rahul Ravindranathan <rahulnathan73@gmail.com>
…tomations-ui Signed-off-by: Rahul Ravindranathan <rahulnathan73@gmail.com> # Conflicts: # tests/e2e_ui/visual/snapshots/test_chat_snapshot/test_chat_conversation_matches_baseline/test_chat_conversation_matches_baseline[chromium][linux].png # tests/e2e_ui/visual/snapshots/test_landing_snapshot/test_empty_landing_matches_baseline/test_empty_landing_matches_baseline[chromium][linux].png # tests/e2e_ui/visual/snapshots/test_sidebar_flyout_snapshot/test_pinned_project_flyout_matches_baseline/test_pinned_project_flyout_matches_baseline[chromium][linux].png # tests/e2e_ui/visual/snapshots/test_sidebar_snapshot/test_populated_sidebar_matches_baseline/test_populated_sidebar_matches_baseline[chromium][linux].png
Signed-off-by: Rahul Ravindranathan <rahulnathan73@gmail.com>
Contributor
|
🏷️ Doc impact: This is a UI display-copy rename ("Scheduled tasks" → "Automations") with the domain model, DB tables, REST paths, and agent tools deliberately unchanged; it's a presentation-string tweak that alters no configurable surface, integration, policy, or documented default. Auto-classified on merge. Set the label manually before merging to override. · run |
12 tasks
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
1 participant
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.
Related issue
N/A — tracked in Linear (OMNI-1193). UI/UX follow-up on the merged Scheduled Tasks backend (#2720) and run-completion tracking (#3014).
Summary
Renames the Scheduled Tasks feature's user-facing name to "Automations" across the web UI. Display copy only — no behavior change.
/v1/scheduled-tasks), stores, agent tools (sys_scheduled_task_*), component/file/hook names, TS types,data-testids, code comments, and the/tasksroute are all unchanged.Why: decouples the product name from the backend contract, so future copy changes never churn the API/schema.
ELI5: we relabeled the buttons and headings to say "Automations" instead of "Scheduled tasks." The wiring behind the buttons still calls it a scheduled task — only the words the user reads changed.
Test Plan
npm run type-check(tsc -b) → 0 errorsnpm run test(vitest) → 117/117 pass across the 4 affected suites (test assertions updated to the new copy, not weakened)/tasksheading, search placeholder, empty state, sidebar nav, command-palette entry, and the New/Edit dialog titles all read "Automations"; route and API calls unchanged.Demo
Type of change
Test coverage
Coverage notes
Pure display-string rename; the 3 affected test suites had their expected literals updated to match the new copy. No new logic to cover.
Files changed (7, +19/−21):
web/src/pages/TasksPage.tsx— h1, search placeholder, load error, loading text, empty statesweb/src/shell/Sidebar.tsx— nav label "Scheduled" → "Automations"web/src/shell/CommandPalette.tsx— "Go to Scheduled tasks" → "Go to Automations"web/src/components/scheduled/CreateScheduledTaskDialog.tsx— dialog titles + fallback error messagesweb/src/pages/TasksPage.test.tsx,web/src/components/scheduled/CreateScheduledTaskDialog.test.tsx,web/src/shell/Sidebar.test.tsx— assertions updated to new copy