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.

[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,