Blog ·

Jira team calendar: what the calendar view shows, and how to fill it

A Jira team calendar is usually the calendar view in a Jira space: a month or week grid showing every work item that has a due date, plus your sprints and releases. Open the space, choose Calendar in its navigation, and the team's dated work is there. What the calendar cannot do is show work that does not exist yet, so the weekly report, the monthly patch window and the quarterly access review only appear once somebody creates them. This guide covers what the calendar view shows, how to schedule work on it, how to share it, and how to keep the routine work on it without anyone remembering to add it.

Statements about Jira are as of October 2026, from Atlassian's own documentation. Atlassian now calls a project a space and an issue a work item. This guide uses both, because most admins still search with the older words.

What the Jira calendar view is #

Atlassian describes it in one line:

Jira's calendar view displays your space's work in a calendar format. You can use the calendar to schedule your team's work, see sprints and releases, and keep track of due dates and deadlines.

So the calendar is a view over work items you already have. It is not a separate calendar product with its own events, and it does not hold meetings, leave or public holidays. Everything on it is a work item, a sprint or a release.

Three facts decide almost everything about how useful it is to a team:

Jira team calendar vs other kinds of team calendar #

People search for "team calendar" meaning several different things. It helps to name which one you need before you set anything up.

What you want to see Where it lives in Jira Fits the calendar view?
When work is due Due date on each work item Yes, this is what it is for
How long a piece of work runs Start date and due date Yes, items span the days
Sprint and release dates Sprints and versions Yes, shown alongside items
Routine work that repeats Has to exist as work items first Only once each item is created
Who is on leave Not a Jira feature No, use your leave or HR calendar
Meetings Your email calendar No
Public holidays Board working days (reports only) No, see Jira holidays

If your question is "what is the team doing and when is it due", the calendar view is the right tool. If it is "who is out next week", Jira is the wrong place and a shared leave calendar will serve the team better. Marketplace calendar apps exist for teams that want both on one grid, at extra cost.

How to open the calendar in a Jira space #

  1. Go to the space your team works in.
  2. Select Calendar in the space navigation. If you do not see it, look under More in the navigation.
  3. Choose the month or week you want, and decide which day the week starts on. Atlassian's configuration page covers searching the calendar, filtering it and the first day of the week.

Filter the calendar to one assignee to get a personal view, or leave it open to see the whole team. Because items appear by due date, a calendar that looks empty usually means the team does not fill in due dates, not that there is no work.

Schedule work on the calendar #

There are two ways to give a work item a place on the calendar.

From the Unscheduled work drawer. Select Unscheduled work in the top right of the calendar. A drawer opens on the right with every item that has no due date. Drag an item onto the day it is due. You can search the drawer, or filter it by assignee, priority and status, which is the quickest way to find the three undated items that matter in a backlog of two hundred.

From the work item itself. Open the item and set its due date. It moves onto the calendar straight away.

To change a date later, Atlassian lists two moves:

That makes the calendar a good place for a weekly planning conversation. Open it on the shared screen, pull the undated items onto days, stretch the long ones, and the dates are saved on the work items as you go.

Sprints and releases on the calendar #

The calendar also shows sprints and releases. You can show or hide each, see their details, and change sprint or release dates from the calendar. For a team running scrum this is the simplest single view of "where are we in the sprint, and what is due before it ends". Our Jira sprint planning guide covers the meeting that fills the sprint in the first place.

Share the team calendar #

Everyone with access to the space can open its calendar, so the simplest way to share it is the link. Two other options are worth knowing:

Atlassian's calendar documentation describes no subscription feed for Google Calendar or Outlook, so if your team lives in an email calendar, plan on the Jira dates staying in Jira. Some Marketplace apps add that sync. Check what one actually syncs, and how often, before relying on it.

The gap: routine work never reaches the calendar on its own #

The calendar shows work that exists. Routine work does not exist until somebody creates it. That is the main reason a team calendar in Jira looks complete in week one and patchy by month three.

Think of the work most teams repeat:

None of these appears on the calendar until a person remembers to create the ticket and set its due date. When that person is on leave, the item is simply missing, and a missing item on a calendar looks exactly like a quiet week. Nobody notices until the report is late.

There are three ways to close that gap.

Option 1: create them by hand, in a batch #

Once a quarter, create every routine item for the next three months, each with its due date, so the whole quarter is on the calendar at once. It is free and it works for a small number of items. It fails the first time the quarter turns over and the batch is forgotten, and it puts dozens of future items into every filter and board in the meantime. Our Jira bulk create guide shows the quickest ways to make many items at once.

Option 2: a scheduled Jira Automation rule #

Jira Automation can create a work item on a schedule, with a due date filled in using a smart value such as {{now.plusBusinessDays(5).jiraDate}}. That puts each occurrence on the calendar the day it is created. The cost is in the details: each run spends automation usage, date arithmetic counts Monday to Friday with no holidays, and dates are worked out in UTC unless you convert them. Our Jira recurring tasks and set the due date automatically guides cover those traps in full.

Option 3: a recurring-work app #

Recurring Work Items for Jira is our app for this job. A project admin writes a rule once: a schedule plus a work item template. The app then creates each work item on time in that one project, and the template sets its due date, picked from a list (The day it is created, 1 day after, 3 days after, 1 week after, 2 weeks after, 1 month after) or written as an expression with the app's tokens. Each item lands on the team calendar with its date already set.

Two things it does that matter for a calendar:

Be clear about one thing: the app creates each item when its occurrence is due. It does not fill the calendar months ahead with future items. The calendar shows this week's routine work; the Next runs preview shows what follows.

Which approach fits #

Situation Best fit
Two or three routine items a quarter Create them by hand in a batch
A few simple schedules, little automation usage elsewhere A scheduled Automation rule
Many routines, holidays that matter, local time zones A recurring-work app
You need leave and meetings on the same grid A Marketplace calendar app, alongside any of the above

When the plain calendar view is enough #

Plenty of teams need nothing beyond what Jira already ships:

A simple setup that works #

  1. Agree that any work with a real deadline gets a due date, and that long work gets a start date too.
  2. Open the calendar in your weekly planning meeting and empty the Unscheduled work drawer of anything that has a date.
  3. Show sprints and releases so the week's deadlines sit next to the sprint end.
  4. Embed the calendar on the team's Confluence home page.
  5. List the routines your team repeats, and pick one of the three options above so each one reaches the calendar without being remembered.

For the routines themselves, our Jira maintenance schedule and Jira weekly report guides show what to put in each recurring item.

FAQ #

Does Jira have a team calendar? Yes, in the form of the calendar view in each space. It shows work items by start and due date, along with sprints and releases.

Why is a work item missing from the Jira calendar? It has no due date. Open Unscheduled work in the top right of the calendar and drag it onto a day, or set the due date on the item.

Can I see several spaces on one calendar? Each space has its own calendar view. For a combined view across spaces, teams use a dashboard or a Marketplace calendar app.

Can the Jira calendar show recurring work? Only once each occurrence exists as a work item. A scheduled Automation rule or a recurring-work app creates each occurrence with its due date, so it appears on the calendar on its own.

Does the Jira calendar sync with Google Calendar or Outlook? Atlassian's calendar documentation describes no such feed. Marketplace apps add one.