DEV Community

Vladimir Letiagin
Vladimir Letiagin

Posted on Edited on

Google Calendar to Jira worklog: log meetings with the issue already picked

Planim Time, a time tracker for Jira on macOS, Windows and Linux, turns Google Calendar meetings into Jira worklogs. It reads the calendar and proposes the issue for each meeting, and one click logs the meeting with its real start time and duration.

Connecting Google Calendar

The sign-in opens in your browser and asks for read-only access. Tick the calendars you want read; the primary one is on by default, so a shared team calendar does not get pulled in by accident. Meetings from the last 30 days and the next 7 then show up next to your worklogs, in the week view and at the bottom of each day's list.

Week calendar in Planim Time: Google Calendar meetings as dashed blocks next to logged Jira worklogs

Google Calendar already knows when each meeting happened and how long it ran. What it lacks is the Jira issue, and a worklog cannot exist without one.

How Planim Time picks the issue

An issue key in the event title is the simple case: PAY-412 refunds sync goes to PAY-412. Most invites have no key, so the app goes further. Pick an issue for a meeting once and it is remembered for the whole series and for other meetings with the same title, so the daily standup asks one time. Meetings with neither a key nor a memory get up to three suggestions by keyword match against your issues, and a default issue takes whatever is left. The reason is shown next to each issue.

A meeting popover in Planim Time: a design review matched to WEB-77 by the word checkout, with Log and Ignore buttons

Nothing is logged until you click Log, and Log all takes the whole day. The result is a native Jira worklog under your account, with the event title as the description.

Tempo Timesheets and Clockwork can show Google events too. Tempo fills in the issue when its key is in the event title, and in Clockwork you choose the issue for every event.

Events are downloaded from Google straight to your machine, and the Planim Time server only brokers the sign-in. Private and confidential events are not read. The walkthrough with every setting is in How to log meeting time in Jira straight from your calendar.

The same thing by hand

Open the event and note the start and the length. Open the issue in Jira, choose Log work, type the duration, change Date started from "now" to the meeting's start, and paste the title as the description. Repeat for the next meeting.

For two meetings a week that is fine. Past that it becomes a Friday job, and on Friday the durations get rounded to the hour and half of them land on the wrong ticket.

Check the direction first

Most Google Calendar integrations for Jira go the other way and put Jira due dates and sprints on a calendar. For time tracking you need the calendar event to end up in Jira as a worklog with the meeting's start time.

Top comments (0)