Item logo image for AI Capacity Planner for Google Calendar

AI Capacity Planner for Google Calendar

ExtensionWorkflow & Planning
Item media 5 (screenshot) for AI Capacity Planner for Google Calendar
Item media 1 (screenshot) for AI Capacity Planner for Google Calendar
Item media 2 (screenshot) for AI Capacity Planner for Google Calendar
Item media 3 (screenshot) for AI Capacity Planner for Google Calendar
Item media 4 (screenshot) for AI Capacity Planner for Google Calendar
Item media 5 (screenshot) for AI Capacity Planner for Google Calendar
Item media 1 (screenshot) for AI Capacity Planner for Google Calendar
Item media 1 (screenshot) for AI Capacity Planner for Google Calendar
Item media 2 (screenshot) for AI Capacity Planner for Google Calendar
Item media 3 (screenshot) for AI Capacity Planner for Google Calendar
Item media 4 (screenshot) for AI Capacity Planner for Google Calendar
Item media 5 (screenshot) for AI Capacity Planner for Google Calendar

Overview

Link Google Calendar events to Jira work items: issue cards, synced dates and time logging.

AI Capacity Planner for Google Calendar connects your Google Calendar with Jira Cloud. Plan meetings and focus time against real work items, see the Jira context right in Calendar, and keep dates and time logs aligned without switching tabs. What it does Link an event to a Jira work item from the title. Start typing in the event title and pick an issue from the suggestions. Search works on the issue summary and on its key (for example "PLAN-16"), and you can filter by space, assignee and status, as in Jira. Create or link from the event. Open an event that is not linked yet: create a Jira work item from it, with or without a parent, choosing type, status and assignee, or link it to a work item that already exists. Summary, description and dates come from the event. See and edit the issue inside Calendar. When you open a linked event, a Jira card shows type, key, summary, status, priority, assignee, epic and description. You can change the status, priority, assignee and epic directly from the card. The data is always read fresh from Jira when you open the event. Jira on every event. In the calendar grid, each linked event shows the issue type and key (click it to open the issue), the assignee, the priority, the status, and a circle with the time you logged on it that day. A real link on both sides. The event shows the issue as its source, which opens it in Jira, and the issue gets a "Google Calendar" web link to the meeting. The key is removed from the event title, so guests see a clean title. Dates stay in sync. Choose which Jira fields follow the event, for example "Start date" and "End date". Move or resize the event in Calendar and the issue is updated within seconds. Change the dates in Jira and the event moves within a few minutes. If both changed, Calendar wins. Log your time where it belongs. Click the time circle of an event to log its time, or to correct or delete what is logged. Log Work logs, in one click, the completed linked events of a day that have no time yet, with the right start time and duration. Native Jira worklogs or Tempo. For each Jira site, choose whether time is logged as Jira worklogs or through Timesheets by Tempo, with your own Tempo API token, so the hours count as yours. Your day at a glance. Next to each date, a circle shows the time you logged that day, compared with your linked events: red when nothing is logged, green when it matches, yellow when it is less. Click it for the details of the day. Why install it Less context switching. Work items, status changes, planning and time logs happen where your day is already organised: your calendar. Planning that matches reality. Event dates and Jira dates no longer drift apart, so boards, timelines and capacity views in Jira reflect what is actually scheduled. Accurate time tracking without effort. Worklogs come from the meetings you actually held, and the circles show at once which events and days still miss time. Works with AI Capacity Planner for Jira. Events linked by either tool are recognised by the other, in the same format. Several Jira sites, one calendar. Connect more than one Jira Cloud site, pick the spaces to work with, and choose for each how time is logged. Privacy and security The extension runs in your browser. It sends no data to Essere Agile or to any server of ours: it talks to Google (Calendar, sign-in and fonts), to your Jira Cloud sites and, only if you choose it for a site, to Tempo. Jira and Tempo access is limited to the sites you enter and allow when Chrome asks. Google access is limited to calendar events and is used only to read and update the events you link. You can disconnect at any time from the extension settings. Your Jira and Tempo API tokens and settings are kept in your browser's extension storage. Privacy policy: https://www.app.essereagile.com/ai-capacity-planner-privacy-policy Requirements A Jira Cloud site (your-site.atlassian.net) and an Atlassian API token. A Google account with Google Calendar, used in Chrome. Optional, to log time through Tempo: Timesheets by Tempo on the Jira site and your own Tempo API token.

Details

  • Version
    1.0.2
  • Updated
    October 22, 2026
  • Size
    361KiB
  • Languages
    English
  • Developer
    Essere Agile
    Via della Liberezione 4 Bologna, BO 40128 IT
    Website
    Email
    mbudri@essereagile.com
    Phone
    +39 331 318 3067
  • Trader
    This developer has identified itself as a trader per the definition from the European Union and committed to only offer products or services that comply with EU laws.

Privacy

Manage extensions and learn how they're being used in your organization

AI Capacity Planner for Google Calendar has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

AI Capacity Planner for Google Calendar handles the following:

Personally identifiable information
Authentication information
Website content

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps