Notice the new Jira Business timeline?

[#1]

If you are using business timeline, you might have notice the new visual changes. Before rolling it out further, we want feedback from active Jira business project users who rely on timeline planning.

New Timeline

Old Timeline

What is changing

• Cleaner layout 

• Unlimited child items (currently we limit at 100 child items) 

• Early groundwork for future features like displaying more fields and date roll-ups.

How you can help

1. Tell us how the new Timeline works for your team in real scenarios.

2. Call out anything that slows you down or makes planning harder.

3. Share gaps where old functionality feels necessary or where new workflows are unclear.

Book here directly for a chat with me or leave you contact below for me to schedule a convenience time (please provide your time zone).

Want early access?

If you do not currently see the new Timeline but want to try it, comment below and we can opt your site into the experiment. Spaces are limited, so we will confirm individually.

Your feedback will directly influence the next iteration. Thanks for helping us shape a Timeline that actually solves real planning problems.

[James Rickards _SN_]

My 2c for what it's worth...

Firstly, be careful of an availability/selection bias due to your request for feedback only from active users.  You should also be asking why users don't use timelines when they could/should.  I would really love to get value out of timelines, but I usually just hide the screen.

The biggest complaint I hear as an admin is the lack of colours!   Where are the colours?  Everyone loves colours and users coming from excel/ppt based management use them extensively. It's the main feedback I get from business users wanting to choose monday.com over Jira.

Now I personally don't really care about colours, so my personal thoughts are that I've found that Timelines involves lots of micromanagement and rework, especially when dates inevitably change. IMO, to reduce this, dependencies need to work more like in Microsoft Project, where changes to dates can optionally cascade through to linked work depending on the type of link (e.g. start with, starts after, finishes with).  I've had to build complex automations to achieve such functionality for users who did use timelines and Advanced Roadmap for larger projects. But with this complexity, staff need to have extreme product technical skills to map out a schedule, which is a barrier to entry if this became an OOTB feature.

Finally, in my experience, execs HATE logging into any work management tool, especially Jira. They also don't want to pay a licence to only log in about once a week for an update on progress. This requires presenting project plans/milestones outside of the Atlassian suite. To do this, most people I've worked with default to a simple corporate branded block diagram in PowerPoint as a Jira Timelines screenshot looks ugly. PM's then need to maintain timelines in two places, but because Jira Timelines takes more effort than PPT, the parallel tracking of time in Jira gets relegated to the scrap heap.

I would suggest an experiment where you have people demo maintaining the same timeline in both Jira and whatever they use to present to their execs and simply observe what slows them down.
- e.g. in PPT you can multi-select several shapes and colour/resize/move them in one go, but in Jira you need to make changes one at a time).

Good luck, and I'm looking forward to seeing whatever changes result from this initiative.