Half of what people search for under "Google Calendar Jira integration" goes the other way: putting Jira due dates and sprints on a calendar. This is about the opposite direction. You have a Google Calendar full of meetings, your team logs time in Jira, and at the end of the week none of those meetings exist in Jira.
That gap is bigger than most people think. Count the meetings in a normal week, multiply by their length, and you get a day or more that never became a worklog. The calendar already knows when each meeting happened and how long it ran. The only missing piece is which Jira issue it belongs to.
Here is what works, from the cheapest option up: by hand, a free Marketplace app, Tempo or Clockwork if you already pay for them, and Planim Time, which remembers the issue per meeting.
By hand, from the calendar
Open the event, note the start and the length. Open the issue in Jira, Log work, type the duration, change Date started from "now" to the meeting's start, paste the title into the comment. Save. Repeat for the next meeting.
It works, and for two meetings a week it is fine. Past that, nobody does it on the day. It becomes a Friday job, and Friday memory rounds everything to the nearest hour and attaches half of it to the wrong ticket.
A free Marketplace app, with one condition
There is a free app on the Atlassian Marketplace called Google Calendar Event to Worklog for Jira Cloud, by Move Work Forward. It reads your Google Calendar and offers events as worklogs. The condition is in the name of the event: it needs the issue key in the title, like PAY-412 refunds sync, otherwise it has nothing to attach the time to.
Its last release listed on the Marketplace is version 1.0.0 from October 2023, and it is Google only. A similar app, WiseLog, is marked unsupported.
Tempo and Clockwork, if you already pay for them
Both big Jira time-tracking apps have Google Calendar connections, and both come as part of the paid product rather than as a standalone feature.
Tempo Timesheets shows your Google events as cards in My Work. A card logs in one click when the event title contains the issue key; otherwise you pick the issue on each card. Private and "free" events are skipped, and the connection is one-way.
Clockwork connects Google and Outlook calendars in its Pro plan. You click an event, pick the issue, and the worklog is prefilled with the meeting's time. There is no key matching documented, so it is a pick per event.
If your organisation already runs one of these, the calendar part is in there.
Clockify and Toggl: calendar events as their own time entries
Both show your Google Calendar next to their own timer. Clockify has "Copy as time entry" on each event; Toggl can create a time entry automatically a few minutes after a meeting starts. The entries land in Clockify or Toggl, not in Jira. Their Jira integrations are browser extensions that put a start button on the issue page, and nothing moves a calendar event into a Jira worklog.
Planim Time: pick the issue once
Planim Time is a time tracker for Jira on Mac, Windows and Linux. It connects Google Calendar with read-only access, and meetings from the last 30 days and the next 7 show up next to your worklogs, in a calendar view and at the bottom of each day's list.
Here is how the issue gets picked. A key in the title still works. On top of that, once you pick an issue for a meeting, the app remembers it for that series and for other meetings with the same title, so the daily standup gets its ceremonies issue once and never asks again. Meetings with neither a key nor a memory get up to three suggestions by keyword match against your issues, and you can set a default issue for whatever is left. Each meeting shows the reason next to the issue. One click logs it, and Log all logs the whole day.
Events are downloaded straight from Google to your machine; the Planim Time server only brokers the sign-in. Private and confidential events are never read. The full walkthrough, including where meeting time should go in Jira in the first place, is in How to log meeting time in Jira straight from your calendar.
Four things to check before you pick
- The direction. "Jira to Google Calendar" is a different product, and most search results are about that one.
- Whether it needs the issue key in the event title. If it does, the whole team has to start naming meetings that way, or the integration covers only a fraction of your calendar.
- Where the event titles go. Some tools store them on their servers, some keep them on your machine. Check the vendor's privacy page.
- What lands in Jira. You want a worklog with the meeting's real start time and a comment; a time entry in another tool never shows up in Jira.
Top comments (0)