More 'Powerful' Timeline braking existing workflows without warning

[Peter Notenbaert]

As you can see in the comments in https://community.atlassian.com/forums/Jira-articles/Upcoming-Unified-More-Powerful-Timeline-for-Jira-Software-Spaces/ba-p/3219209 this new timeline is braking existing workflows for multiple people and teams. Without any warning, sometimes at a very critical time in their process.

This is not a small thing, it completely changes the way team used the timeline to plan they work! According to me, totally unacceptable. 

Can it be rolled back, until it is usable and production ready again: support the existing flow?

[Marc -Devoteam-]

Hi @Peter Notenbaert 

Provide feedback to Atlassian on this.

Here on the public community forum we don't have influence or can solve this.

Note on the the topic, see that there will be: "Enhanced filtering (Sorting and Grouping are coming soon!)"

Filter and group work items by more fields to quickly find what matters and organise your timeline your way. Sorting currently supports specific work item fields(key, summary, assignee and status); we will add more soon.

So then you will be able to filter or group what you see.

[Davit Mkrtchyan - Be On Time]

Hi Peter - I feel this one, it is genuinely frustrating when a change lands mid-flight on a critical week.

Straight answer first: no, you cannot roll this back yourself. It is a server-side change from Atlassian, so there is no toggle on your side, and Marc is right that the forum has no lever here either. What actually gets traction is a support ticket plus a vote on the related change request - and make it concrete, not general: "X used to nest under Y, now it does not, and here is what it broke for us." That framing gets reviewed; "please revert" usually does not.

But honestly, waiting for the "sorting and grouping coming soon" fix will not fully protect you, and it is worth saying why: the Timeline is a view that Atlassian reshapes on their own schedule. Anything critical you hang directly off it is exposed to the next update too. This will happen again.

So a few things I would do right now to take the sting out of it:

• Stop letting the Timeline be your source of truth for dates. The deadlines you actually owe people belong in fields on the issues - start date, due date, a baseline date. Fields survive view changes; layouts do not.
• Drive your stakeholder reporting off a saved filter or dashboard gadget built on those fields, not off a Timeline screenshot. Next time the view shifts, your report does not move with it.
• If the child-under-Epic nesting specifically broke, double-check the items are linked by the real parent field (not a label or a generic link) - some of the recent changes shifted how Timeline resolves hierarchy between team-managed and company-managed projects.

The bigger picture: your Timeline is quietly doing two jobs. One is the day-to-day operational view - fine to let that evolve with Jira. The other is your schedule of record - the dates you promised a steering committee - and that one needs to live in data you control, not in a UI that can change over a weekend. Split those two and a change like this becomes an annoyance instead of a fire.

Hope some of that helps take the pressure off this week.