How to Schedule Jira Issues in Google Calendar in 2026: 5 Ways

Jira doesn't sync with Google Calendar on its own, so you have five ways to get issues onto your calendar: create the event by hand with the issue link in it, subscribe to an iCal feed from a Jira Marketplace app, run a two-way sync app, build a Zapier automation, or let a planner like Reclaim.ai turn each issue into a time block.

The gap is familiar to anyone who works in sprints. The board says what you own, the calendar says where your day went, and the two never talk, so the issue that mattered most gets whatever's left after meetings. This guide covers each method step by step, what it costs, where it breaks, and which one fits a solo developer, a team lead or a whole squad.

Can Jira sync with Google Calendar natively?

No. Jira Cloud has a built-in Calendar view, but it lives inside Jira and doesn't push anything to Google Calendar. Atlassian's calendar view documentation says you open it from your space navigation, and that it only shows work items scheduled with the Start date and Due date fields. Items without those dates don't appear, and unlike the calendar in Plans, it ignores inferred sprint or release dates.

Check that view before paying for an app. If your team only needs to see when work lands, the Jira calendar may be enough. The trouble starts when you want issues next to your meetings, because that's where your day actually gets decided, and the Jira calendar can't see your meetings at all.

How to add a Jira issue to Google Calendar by hand

The quickest way to schedule one Jira issue is a normal Google Calendar event with the issue key in the title and the issue link in the description. It costs nothing and takes under a minute, and Google's create an event guide covers the basics.

1. Open the issue in Jira and copy its link from the browser's address bar (it ends in the issue key, such as /browse/WEB-212).
2. Open Google Calendar and click Create (upper left), or click an empty slot in Day or Week view.
3. Type a title that starts with the issue key, then a short name: WEB-212 Fix checkout redirect.
4. Make the event as long as the focused work the issue needs, not the time left until it's due.
5. Paste the Jira link into the description so the event opens straight to the issue.
6. Click Save.

I put the key first in every block title. When I search my calendar on Friday for what I actually worked on, typing the project prefix pulls up the whole week's blocks in one list, and the key is what my standup notes use anyway.

Manual events have one real weakness: nothing updates. If the issue slips to next sprint or someone reassigns it, the event stays put until you move it. That's fine for the two or three issues that carry your week. It falls apart for a full sprint.

How to subscribe to a Jira calendar feed in Google Calendar

A calendar feed shows Jira issues in Google Calendar as read-only events that refresh on their own. Atlassian's calendar documentation describes no export or feed, so you need a Marketplace app such as Calendar Sync for Jira, whose listing says each feed is built from a JQL query and works with Google Calendar, Outlook and phone calendars.

1. A Jira admin installs a feed app from the Atlassian Marketplace (Calendar Sync for Jira is a paid app with a free trial).
2. In the app, create a feed and give it a JQL query, for example assignee = currentUser() AND resolution = Unresolved.
3. Copy the feed's calendar address.
4. In a desktop browser, go to Google Calendar. Beside Other calendars, click Add other calendars, then From URL.
5. Paste the address and click Add calendar. The feed appears under Other calendars on the left.

Google's help page on adding a calendar by link is clear that this only works in a web browser: subscribing isn't possible in Google's mobile apps for Android, iPhone or iPad. Do the setup at a desk, not between meetings on your phone.

A feed is the right choice when you want to see deadlines, not plan around them. It only reads from Jira, so dragging an event in Google Calendar changes nothing in Jira. When I first set one up, I made the mistake of feeding in every open issue in the project. The calendar turned into wallpaper. Narrowing the JQL to my own unresolved issues with a due date fixed it.

How to sync Jira and Google Calendar both ways

Two-way sync means a change on either side shows up on the other: drag a calendar event to Thursday and the Jira dates move to Thursday too. That takes a Marketplace app built for it, such as Google Calendar Bridge for Jira by BrizoIT.

According to its Marketplace listing, Google Calendar Bridge for Jira:

• Syncs in both directions every two minutes, so you can reschedule by dragging an event in Google Calendar.
• Creates events from Jira date and date-time fields, including custom fields, using a start field alone or a start and end field.
• Picks the work by project, saved filter or JQL, with up to 100 bridges.
• Runs on Jira Cloud and is a paid app, billed through Atlassian.

Two-way sync suits teams where a lead plans releases or on-call rotations on a shared calendar and wants Jira to follow. It's the most powerful option here and the easiest to get wrong. Before I'd turn it on for a team, I'd agree on which date field owns the schedule, because an event dragged by accident is now a changed due date in Jira.

How to send new Jira issues to Google Calendar with Zapier

Zapier can add an event to Google Calendar whenever something happens in Jira Software Cloud. Its Jira and Google Calendar integration page lists Jira triggers for New Issue, New Issue (Via JQL), Issue Status Changed and Updated Issue, and Google Calendar actions including Create Detailed Event, Quick Add Event and Update Event.

1. In Zapier, create a Zap and choose Jira Software Cloud as the trigger app.
2. Pick New Issue (Via JQL) and enter a query that matches only the issues you want on your calendar.
3. Choose Google Calendar as the action app and pick Create Detailed Event.
4. Map the issue key and summary to the event title, the issue link to the description, and the due date to the start time.
5. Test the Zap with a real issue, confirm the new event looks right on your calendar, then turn the Zap on.

Zapier's Free plan covers this, since it's a two-step Zap. Free caps you at 100 tasks per month and checks Jira every 15 minutes, so a new issue can take a while to appear. Multi-step Zaps, such as also posting to Slack, need the Professional plan or higher.

The catch is that a Zap like this creates events and then forgets them. If the due date moves, the event doesn't, unless you build a second Zap on Updated Issue that finds and updates it. Also think about where the event lands: an event at the due date tells you when the work is due, not when you'll do it.

How to auto-schedule Jira issues as time blocks

An auto-scheduling planner reads your assigned Jira issues and books working time for each one around your meetings. Reclaim.ai's Jira integration does this in Google Calendar and Outlook: assigned issues become protected time blocks, the Jira estimate (story points, hours or t-shirt sizes) sets how long each block is, and due dates and priority decide the order, within the active sprint.

To use it, Reclaim's help center lists a Reclaim Starter plan or higher, a Jira account in an Atlassian organization with Rovo (Atlassian's AI features) enabled, and an Atlassian admin who can allowlist Reclaim's callback URL. Then you connect Jira under Settings → Integrations in Reclaim. On Reclaim's pricing page, Reclaim Starter runs $10 a seat when paid yearly and $12 a seat when paid month to month, and the free Lite plan doesn't include Jira.

Akiflow is a planner of a different kind, if you'd rather manage issues in a task list than have them booked for you: it imports Jira issues into its task list, filtered by assignee and status, and can map its scheduled and deadline dates to Jira fields. Its help article says the two are synced both ways, and when you finish a task in Akiflow it offers to mark the issue done in Jira too.

Planners earn their price when your calendar is crowded and issues keep getting squeezed out. They need good inputs, though. An issue with no estimate gives the planner nothing to size, so the habit that matters is estimating before the sprint starts. Reclaim isn't the only option in this space; the Reclaim.ai alternatives page compares the others.

Which way should you schedule Jira issues?

Pick by what you need the calendar to do. My own choice for solo work is the manual route for the issues that matter and nothing for the rest. After sprint planning I give each of my top issues a block before lunch, when my calendar is usually quietest, and let the small tickets fill gaps.

• You want to see deadlines next to meetings: an iCal feed with a tight JQL query.
• Your team plans on a shared calendar and wants Jira to follow: a two-way sync app, with one agreed date field.
• You want an event for every new issue that matches a rule: a Zapier automation.
• Your issues keep losing to meetings: an auto-scheduling planner, if your Atlassian admin will approve it.
• You only care about two or three issues a week: manual events with the link in the description.

Why Jira issues aren't showing up in Google Calendar

Missing issues almost always come down to dates, filters or permissions. Start with the first check; it explains most cases.

1. No dates on the issue. Jira's own calendar needs both Start date and Due date, and the feed and sync apps above build events from date fields too. An issue with no date has nothing to place.
2. The JQL doesn't match. Run the same query in Jira's issue search. If the issue isn't in the results, it won't be in the feed or the Zap either.
3. You tried to subscribe on a phone. Adding a calendar by URL only works from a desktop browser.
4. The feed calendar is hidden. Under Other calendars, make sure the feed's checkbox is ticked.
5. Zapier hasn't run yet. On the Free plan Zapier checks every 15 minutes, and a Zap that used its 100 monthly tasks stops until the next month.
6. The app needs approval. Depending on your Atlassian settings, Reclaim may need a Jira or Atlassian admin to approve it, and Marketplace apps are installed by an admin.

Tips for time-blocking Jira work in Google Calendar

• Size the block from the estimate, then add a margin. A block that's always too short teaches you to ignore your calendar.
• Leave room between blocks. The first sprint I time-blocked, I booked issues back to back and had no space for code review, so now review gets its own slot.
• Keep the issue key in every event title so blocks are searchable later.
• Use a separate calendar or color for Jira work so meetings and issue time are easy to tell apart.
• Put blocked or waiting issues on the calendar as a reminder to chase, not as working time.

For more on keeping that time protected, see how to add Focus time in Google Calendar. For alerts and other things the calendar can do on its own, the guide on automating Google Calendar picks up where this one stops.