I've an urgent issue in Gantt Chart.
Unfortunately we cannot solve the sort.
Initially we solved putting the number before task name, but if you see the task 6,7,8 is after the 050 but it should be after 005.
Please can somebody kindly help us?
It is really an urgent feature otherwise we should consider a different product.
I am experiencing the same issue; using sort by another column in the modelling ribbon used to work but doesn't seem to work now. The problem doesn't affect other visualisations like the charts. Any help on this would be greatly appreciated.
Unfortunately this action does not affect any reaction to Gantt Chart, as you can see from the screen below (sorry but it is in italian) I choose ID column, then Sort by Column -> then I choose "Nome Task" (task name).
In the modeling i see that effectively the rows was sorted by the correct way, but Gantt completely ignore any sorting.
The last time I used this was about 2 weeks ago at which time it was possible to choose which column to sort by, by clicking on the ... at the top-right of the gantt visualisation, but this option no longer appears:
So it seems that something has changed; is there a team at Power BI or GitHub or somewhere else that could advise if/when the functionality will return?
I came across the same issue and reached out to the software engineer of the visual noting the problem and he replied sayingthe following:
Gantt chart doesn’t support custom sorting. This visual always sorts values by date or category if date field isn’t filled.
We’ll improve Gantt visual and allow custom sorting.
Identified a bit of a workaround; by selecting group tasks, it seems that tasks are sorted alphabetically by legend first then by date second. It may be necessary to make all task names unique otherwise it will combine tasks with the same name (unless of course you want this to happen). And, by using a helper column to assign the right alphabetical value to the field used in the legend, you can determine the required sort order.
That said, this is probably not the intended use of the legend field so the functionality may change at a later update...