Home
›
Timeline for Jira
Team timelines and scheduling

Timeline for Jira: Plan People and Teams Across Projects

See who is working on what, and when, across all your Jira projects. Every person gets one row with their work from every project, every team gets its own row, and a clash shows up the moment two plans land on the same week.

30-day free trial on the Atlassian Marketplace.

Two weeks of work from three Jira projects, Platform, Mobile app and Data, first as each project sees it in Jira, then in the ActivityTimeline Planner with one row per person. Each project looks fine on its own, but Ana Duarte has work from all three projects in the second week: 48 hours for a 40-hour week. Dragging Billing export to Leo Wagner on the same dates brings Ana to 70% and Leo to 90%, and Release 4.2 still ships on Friday.

Same two weeks, same Jira work, two ways to look at it. Jira shows each project's work on its own. ActivityTimeline puts every project on each person's row and each team's row, so clashes show up before the week starts.

Personal and team timelines

See a Jira Timeline by Person, by Team, or Both

The Planner is cross-project from the start: it shows every Jira work item, event and day off assigned to the people or teams you pick, whichever project it comes from. Switch the view to match the question you're answering.

Users

Personal timelines

One row per person, with their Jira work from every project, time off and other events, and a workload indicator under the name.

Best for: team leads who assign and balance work week to week.

Teams

Team timelines

One row per team, with its total workload. Put an epic on a team before you know who will do it.

Best for: PMOs and department heads planning quarters and portfolios.

Team with Users

Both at once

The team's row on top, its people below. Hand team work down to people as the plan firms up.

Best for: delivery managers turning a quarterly plan into weekly assignments.

The Planner for the Platform team over four weeks. Users view: Ana, Leo, Priya and Tom, each with Jira work from the Platform, Mobile app and Data projects, time off, a booking and a placeholder, and a weekly workload indicator. Teams view: Platform, Mobile, Data and QA with weekly team workload. Team with Users view: the Platform team's own work on top, its four people below.

When plans change

Reschedule Jira Work Across People and Projects

Plans move. Drag one item to another day or person, or move a whole project in one go. The new dates and assignee go back to the Jira issue, and time off stays where it is.

Planner, Users view, three weeks from 23 November. A bulk reschedule moves every Mobile app item one week later, including a placeholder, while Ana's vacation and Tom's day off stay put. PLT-131 is blocked by PLT-128 in Jira but was scheduled before it, so it carries a warning until it is moved after its blocker. Leo has one overdue issue, shown by the red counter next to his name.

One item

Drag to reschedule or reassign

Drop a work item on another day or another person's row. The Planner updates the Jira issue's dates and assignee, and every workload indicator updates as you drop.

Drag-and-drop scheduling

A whole project

Move everything at once

Shift a project's issues, bookings, placeholders and notes forward or back, reassign them, or clone them to someone else. Days off, holidays and sick leave are never moved.

Bulk reschedule

What slipped

Catch overdue and blocked work

A red counter next to each name shows open issues past their due date. A warning marks work scheduled before the Jira issue that blocks it.

What it can do

What You Can Do with Team Timelines in ActivityTimeline

Each capability has its own page with the detail: how teams use it and how to set it up.

Bring three projects that share people. See them on one timeline.

In a 25-minute demo, a product specialist builds the view on a setup like yours and answers your rollout and security questions.

Planner with the Milestones Panel open for two weeks from 30 November: releases Mobile 3.8 on 4 December and Platform 12.1 on 9 December, Sprint 24 and Sprint 25, due dates for PLT-128 and DAT-27, a customer demo and a security audit. Below, Ana, Leo and Priya's Jira work. PLT-136 is planned for the week of 7 December but is not in a sprint until it is dragged onto Sprint 25.

Milestones, releases and sprints

Jira Milestones, Releases and Sprints Above the People Doing the Work

The Milestones Panel sits on top of the Planner. It shows what has to land and when, right above the people who have to land it, so a release date and an overloaded week are never on different screens.

Releases

Jira Fix Versions for the projects you pick, each linked to its Jira release page.

Sprints

Each Scrum sprint across its dates. Drag an issue onto a sprint and its Sprint field changes in Jira.

Due dates

Jira issues by due date, in bold as the deadline gets close.

Your own milestones

Demos, deliveries and deadlines, with your own milestone types.

From this week to next year

Long-Term Jira Timelines, From This Week to Next Year

The same rows work at every distance. Look at the next two weeks issue by issue, or at a quarter or a whole year with each person's work grouped into one block per project or epic.

Planner for four people over 2027. Each person works on several Platform, Mobile app and Data epics in turn, with vacations in between. Over a quarter or a year, each person's work is grouped into one block per project or per epic, such as Platform for the first months and Data from August. Over two weeks, each Jira issue shows on its own with its key and title.

Built with

The ActivityTimeline Modules Behind Team Timelines

The Planner does the scheduling. Reports and Workspace turn the same plan into answers for leadership and a clear week for each person.

Works alongside the plans you already keep

ActivityTimeline reads and writes the same Jira fields your other tools use, so project managers keep their view and you add the people view.

Jira timeline and Jira Plans

Keep them for roadmaps and dependencies; the Planner shows who holds the work and when.

Start and end date fields

Map your Jira date fields, and dates set in Jira or in a date-based Gantt app appear on the rows.

Jira Team field

Work assigned to a team in Jira lands on that team's row.

Google Calendar and Outlook

Meetings and out-of-office come in and count toward each person's week.

Jira Timelines in ActivityTimeline: Questions

Answers about people and team timelines, scheduling, milestones and sharing in ActivityTimeline.

Still have a question?

Contact us through the support portal
Can ActivityTimeline show one timeline across all our Jira projects?
Yes. The Planner is cross-project by default: it shows every Jira work item and event assigned to the people or teams you select, whichever project it comes from. Filter it to one or several projects when you want to focus, and it works on any Jira plan.
Is there a separate timeline for each Jira project?
No. Timelines in ActivityTimeline are organized by people and teams, because that is where clashes show up. To see one project, filter the Planner to it, or group each person's bars by project so every project shows as its own colored block.
How does Jira work get onto the timeline?
Drag issues from the Issue Panel onto a person or a team. Issues that already have start and end dates in Jira appear on those dates once the date fields are mapped, and issues in a sprint can appear across the sprint's dates without manual scheduling.
Do changes on the timeline update Jira?
Yes. Scheduling or moving an issue to a person sets its assignee and its start and end dates in Jira, and dragging an issue onto a sprint in the Milestones Panel updates its Sprint field. Changes made in Jira show up on the timeline in turn.
Can we see releases, sprints and deadlines on the timeline?
Yes. The Milestones Panel above the people rows shows Jira Fix Versions as releases, Scrum sprints across their dates, issues by due date and your own milestones, such as demos, deliveries and deadlines.
Does ActivityTimeline show dependencies?
It tracks Jira's blocks and is blocked by links. When a blocked issue is scheduled before the issue that blocks it, the bar shows a warning. The links themselves are created in Jira.
We already use Jira Plans or a Gantt app. Do we need both?
Many teams keep Jira Plans or a Gantt app for roadmaps and dependencies, and use ActivityTimeline to see who holds the work and when. They use the same Jira fields, so nothing is planned twice.
Can we share or export the timeline?
Yes. Save a view with its teams, filters and period, and share it with people, teams or roles, or by link. The Timeline Report exports a team's rows to Excel, and ActivityTimeline reports can sit on Jira dashboards and in Confluence pages.
How do we try it?
Start a 30-day free trial from the Atlassian Marketplace on your own Jira projects; no credit card is needed. Or schedule a demo, and a product specialist shows team timelines on a setup like yours.

See All Your Jira Projects on One Timeline, by Person and Team

Install ActivityTimeline from the Atlassian Marketplace, pick a team that works across several projects, and see its next four weeks on your own Jira data. Start with one team, then roll out to the whole company.

30-day free trial, no credit card. Questions first?

Talk to support

Platform team, next four weeks after rescheduling: each person's weekly workload across the Platform, Mobile app and Data projects, with nobody over 95% and Release 4.2 on track.