Timeline View Reversion

[joshua_k_twumasi]

The recent changes to Timeline have made it significantly less usable for our team.

Overnight, we’ve lost key capabilities such as filtering and grouping by Epic, which are fundamental to how we plan and track work. As a result, the Timeline view is now far less effective and difficult to navigate.

This is particularly concerning given the timing. We are about to begin Product Increment planning for Q3, and these changes have introduced friction at a critical moment.

Could you clarify:

• Whether this change is intentional or a temporary regression?
• If there is a way to restore the previous functionality (e.g., via settings or feature flags)?
• Whether a rollback or fix is planned in the near term?

We rely heavily on Timeline for planning, and this change has had an immediate impact on our workflows.

[Arkadiusz Wroblewski]

Hello and welcome to Atlassian Community @joshua_k_twumasi 

You're right, this is part of the new unified Timeline rollout. Atlassian has acknowledged the disruption caused by moving the filtered hierarchy to a glance panel and is tracking this regression under JRACLOUD-98720.

There is no native admin setting to revert to the old view, so watch that ticket for updates.

Best,

Arek 🤠

[joshua_k_twumasi]

Im not sure this ticket addresses the issue.

[Anastasiia Dimnych]

Hi @joshua_k_twumasi,

I have just created a support ticket PCS-3803860 on your behalf, check your email for further communication. 

Best,

Anastasiia

[joshua_k_twumasi]

Thank you so much!

[Davit Mkrtchyan - Be On Time]

Hi @joshua_k_twumasi Joshua -

I really feel for you here. Losing your primary visibility tool right and before Q3 PI Planning is a nightmare. When you are coordinating multiple teams for a Product Increment, friction in the tool often translates into actual risk for the delivery date.

While waiting for the fix on JRACLOUD-98720, I would like to offer a perspective that might help you navigate the next few weeks.

The core issue here is a common trap in Jira: treating the Timeline as a planning engine.

The built-in Timeline is essentially a visual aid - it is designed to show where things are. But for PI Planning, you need a deterministic scheduling engine - something that handles dependencies, groupings, and critical paths regardless of which UI update Atlassian pushes overnight.

If your Q3 planning is too critical to be put on hold by a UI regression, I would suggest two immediate paths:

1. The Emergency Path: If you have Jira Premium, try leaning more heavily on Advanced Roadmaps (Plans), which generally has more stable filtering and hierarchy logic than the basic Timeline view. It is not a perfect fix, but it might bridge the gap for your PI sessions.

2. The Strategic Path: This is a signal that your process has outgrown the built-in visual tools. For high-stakes planning (especially with the complexity of PI planning), it is usually safer to move the brain of your schedule into a professional planning layer. When the logic is decoupled from the basic UI, a unified rollout of a view does not break your ability to track work.

I have seen many teams go through this Timeline heartbreak right before big milestones. The lesson is usually the same: the more critical the planning, the less you should rely on a visualization tool for the actual governance of the project.

Wishing you a smooth (and stable) Q3 planning!

[joshua_k_twumasi]

Hi,

Thanks for taking the time to respond and for acknowledging the impact this has on our upcoming Q3 PI Planning.

While I appreciate the suggested workarounds, I think it's important to separate the wider discussion about planning tools from the issue being raised here.

The challenge isn't that we're using Timeline as a planning engine or that our process has outgrown the tool. The challenge is that a capability we previously relied upon has changed in a way that has significantly reduced the visibility and usability of the feature for our teams.

We use Jira based on the functionality available to us at the time, and over time our planning and governance processes naturally evolve around those capabilities. When a change is introduced that removes or degrades those capabilities, particularly with limited notice and close to a major planning event, it creates disruption regardless of whether alternative tools or approaches exist.

Advanced Roadmaps may help as a temporary workaround, but that doesn't address the underlying concern that a previously working feature has regressed. From our perspective, the key questions are:

• Is the behaviour reported in JRACLOUD-98720 considered a defect or an intentional product change?
• Does Atlassian recognise the loss of capability experienced by customers impacted by this change?
• Is there a planned resolution or restoration of the previous behaviour?
• What is the recommended path for customers who have built planning processes around the functionality that was available before this update?

I fully understand that products evolve, but when changes materially affect established workflows, especially for enterprise planning activities, it's important that customers receive clear communication, ownership, and a path forward.

We'll continue to monitor JRACLOUD-98720, but I'd appreciate any additional information you can provide regarding remediation plans and timelines for resolution.

Thanks,

[Davit Mkrtchyan - Be On Time]

Hi @joshua_k_twumasi Joshua -

You are absolutely right, and I appreciate you calling that out.

I apologize if my previous response felt like a diversion from the immediate issue. You are 100 percent correct: regardless of how a tool is positioned, if a capability you rely on is removed or degraded without notice - especially right before a major event like PI Planning - it is a failure in the user experience.

Just to be clear and avoid any confusion: I am not an Atlassian employee, but a partner and community member. Because of that, I do not have inside access to their internal product roadmaps or the ability to provide official answers on whether this specific change was intentional or a regression. I wish I could give you those definitive answers and timelines, but I am in the same boat as you, monitoring the public tickets for updates.

I completely agree that visibility should not be a moving target, and that established workflows should be respected during updates.

I really hope Atlassian provides a clear path forward for you and your team quickly. Best of luck with the Q3 planning - I hope you manage to navigate it despite this friction.

[Mary from Planyway]

@joshua_k_twumasi 

Hi,

Unfortunately, this appears to be an intentional product update rather than an isolated issue on your site. Atlassian recently announced the rollout of a unified Timeline experience for Jira Software Spaces, introducing changes such as support for subtasks, work items outside epics, inline editing, and enhanced filtering. They also noted that grouping and sorting capabilities are still being rolled out, with additional improvements planned. (Atlassian Community)

At the moment:

• There isn't a setting or feature flag to restore the previous Timeline experience.

• Atlassian hasn't announced a rollback of the new Timeline.

• They are actively collecting feedback, and several users have reported the same concerns around losing Group by Epic and the previous hierarchy behavior. Atlassian has acknowledged this feedback, and there is an open suggestion/bug for the regression. (Atlassian Community)

Since you're about to start PI planning, you may also want to consider using Planyway for Jira. It provides an interactive timeline with grouping by epics, customizable views, dependencies, workload management, and cross-project planning. Unlike the native Timeline, you can save custom views and share them with your team, making it a good option for roadmap and PI planning while Atlassian continues evolving the new Timeline experience.

I would also recommend adding your feedback to Atlassian's announcement thread and voting for the related issue so the product team can better understand how these changes are affecting planning workflows.

[Joshua Brock _ Seibert Group_ GmbH]

Greetings @joshua_k_twumasi ... from one Joshua to another, great point!

To answer your direct questions as best the community can ... this is tied to the new unified Timeline UI that Atlassian is rolling out, and several teams are reporting the same regression.

The most useful concrete steps right now are to file a support ticket to opt out of the new Timeline while the gaps are being worked through, and to add your voice to the official change thread and the related JRACLOUD tickets. That feedback is the channel the product team actually tracks, and enterprise PI planning is a strong case to make while the decision is still in motion. In the meantime, Advanced Roadmaps/Plans can partially cover Epic grouping as a stopgap.

Stepping back from the immediate bug, if your team relies this heavily on Timeline specifically for Program Increment planning, it may be worth looking at a tool purpose-built for that, so a single Atlassian UI change doesn't put your planning cadence at risk. That's what our app, Agile Hive, is built for.

A dedicated PI planning board and native PI execution, rather than repurposing the software Timeline for it. The full Portfolio → Solution → ART → Team hierarchy enforced by the data model, so Epic-level grouping and roll-ups are structural, not dependent on a view toggle. Runs entirely inside Jira with no separate system of record and no data sync. End-to-end SAFe coverage including Lean Portfolio Management, not just planning. And last but not least, lower total cost of ownership than enterprise platforms like Jira Align, and deploys in days to weeks.

There's more on our website, and a free trial on the Atlassian Marketplace if you want to see whether it fits your Q3 cadence.

To note, specifically, that I work at Seibert Group, the team behind Agile Hive.

Hope this helps,

Joshua
Content Writer & US Representative
Agile Hive and Aura Apps (products of Seibert Group GmbH)