Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates user-facing UI labels to rename the “Route Planner” page experience to “Transportation Schedule” (while keeping internal identifiers like routes, file paths, and API method names unchanged) so the UI terminology better reflects a schedule-focused dashboard.
Changes:
- Updated the Route Planner page title (Awesome Bar/global search label) to “Transportation Schedule”.
- Updated key UI strings in the Route Planner page JS (loading text, default-plan help text, and the main header title).
- Updated Fleet workspace shortcut/link labels and the Route Plan DocType field description to reference “Transportation Schedule”.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
one_fm/operations/doctype/route_plan/route_plan.json |
Updates the is_default field description to reference “Transportation Schedule”. |
one_fm/one_fm/workspace/fleet/fleet.json |
Renames Fleet workspace shortcut/link labels to “Transportation Schedule”. |
one_fm/one_fm/page/route_planner/route_planner.json |
Updates the Page title to “Transportation Schedule”. |
one_fm/one_fm/page/route_planner/route_planner.js |
Updates visible UI text (loading text, dialog field help, and header title) to “Transportation Schedule”. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
NoBoneZ
approved these changes
Jun 9, 2026
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
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.
Is this a Feature, Chore or Bug?
Clearly and concisely describe the feature, chore or bug.
Rename the frontend UI from "Route Planner" to "Transportation Schedule" across all user-facing labels — page title, header, loading text, workspace shortcuts/links, and DocType field descriptions — so the terminology accurately reflects its function as a time-based scheduling dashboard.
Analysis and design (optional)
No design changes. This is a text-only rename affecting UI labels. Internal code identifiers (file names, API paths, CSS IDs, variable names) are intentionally preserved to avoid breaking changes.
Solution description
4 files modified:
one_fm/one_fm/page/route_planner/route_planner.jsontitlechanged from "Route Planner" → "Transportation Schedule". This drives the Awesome Bar / global search result label.one_fm/one_fm/page/route_planner/route_planner.jsis_defaultfield description (line 1819), and the main header title#rp-title(line 2279).one_fm/operations/doctype/route_plan/route_plan.jsonis_defaultfield description updated to reference "Transportation Schedule" instead of "Route Planner".one_fm/one_fm/workspace/fleet/fleet.jsonIs there a business logic within a doctype?
Output screenshots (optional)
N/A — text-only rename. After clearing cache:
Areas affected and ensured
is_defaultfield help textis_defaultcheckbox descriptionIs there any existing behavior change of other features due to this code change?
No. All changes are cosmetic label renames. The page URL (
/app/route-planner), API endpoints, file paths, and all internal logic remain unchanged.Did you test with the following dataset?
Was child table created?
No.
Did you delete custom field?
Is patch required?
(No data migration needed — changes are in JSON fixture files and client-side JS labels that sync on
bench migrate/ cache clear.)Which browser(s) did you use for testing?