On gantt views, changing the timescale (3M, 6M, 1Y, Fit, Custom) does not save automatically. Users must explicitly click Save changes for the new timescale to persist.
This is inconsistent with custom roadmaps, where the same kind of view adjustment is auto-saved.
The inconsistency makes gantt feel less polished and less predictable than other roadmap views.
Users can believe their preferred view state was captured when it was not, creating repeat setup work and avoidable confusion.
This is especially noticeable for customers who move between custom roadmaps and gantt and expect the same save behavior.
Auto-save gantt timescale changes so they persist immediately after selection, matching the behavior already implemented for custom roadmaps.
The preferred UX pattern should be that changing only the timescale is treated as a persisted view preference, not as a separate unsaved edit requiring an additional confirmation step.