If you've ever tried to rename a chart axis only to watch the wrong one change, you know the frustration. This user's struggle with a Gantt timeline is not a personal failure, it is a design flaw baked into tools that treat data as a static grid rather than a living model. The problem is clear: the software interprets your intent incorrectly because it lacks the contextual awareness to distinguish between horizontal and vertical axis edits. That is not your fault. It is the fault of a system that expects you to think like a spreadsheet instead of a person.
What this means in practical terms is that you spend time fighting the tool instead of building the timeline. Every click becomes a test of patience. You follow instructions to the letter, and the software still rewrites your work. The user who posted this question did everything right. They received clear steps, executed them, and hit a wall at the final step. The wall is not a knowledge gap, it is a usability gap. Traditional spreadsheets were not designed to handle this kind of task gracefully. They were built for rows and columns, not for visual storytelling. A Gantt chart demands that the tool understand relationships between dates and tasks, not just numbers in cells.
Our opinion is straightforward: you should not have to wrestle with axis labels to get a timeline to work. A modern tool should let you rename the horizontal axis without triggering a cascade of unintended changes. It should recognize that when you click "horizontal axis," you mean the horizontal axis. That seems obvious, but it is not how legacy tools behave. They treat all axes as interchangeable parts of a rigid chart object, so a change intended for one axis can ripple through the entire chart. This is why the user's vertical axis kept shifting: the software could not separate the two.
For anyone building a Gantt timeline, the practical takeaway is this: if your tool fights you on axis labels, it is time to evaluate whether the tool is worth the effort. A spreadsheet should empower your workflow, not add friction. The user who posted this question deserves a solution that works on their terms, not a workaround that requires memorizing hidden menus or arcane settings. The industry can do better, and users should demand it.