How to log Outlook and Teams meetings to Jira as worklogs
Someone asked Atlassian Community in 2019 how to log time from an Outlook calendar appointment to Jira. People are still asking in 2025, on the Toggl forum too, and the answers have not improved much: a Tempo link, an Outlook add-in that has since disappeared, and "create a Meetings ticket". The confusion starts with the word "integration". Atlassian's own Outlook add-in is about issues and email: create an issue from a message, see issue details in the sidebar. It does not log time. Most "Jira Outlook calendar" results are about getting Jira due dates and sprints into Outlook, again the wrong direction. What the question means is: I have an Outlook calendar full of Teams meetings, my hours live in Jira worklogs, how do I get one into the other. The options today are by hand, Tempo, Clockwork, and Planim Time connected to Microsoft 365; Toggl and Clockify show the calendar but stop before Jira. The manual way, and why it fails Open the appointment, note start time and duration. Open the issue, Log work, type 45m, set Date started to when the meeting began (it defaults to now, which is how worklogs end up claiming you were in the morning standup at six in the evening), paste the subject as the comment. Save. For one meeting that is a minute. A week of them usually waits until Friday, and by then the times come from memory instead of the calendar. Tempo, if your organisation runs it Tempo Timesheets has a Microsoft 365 calendar connection. Your Outlook events appear as cards in My Work. Events with an issue key in the subject log in one click; for the rest you choose the issue on the card. Two things to know from Tempo's own docs: it works with Microsoft 365 in the cloud, not with on-premises Exchange, and an organisation-wide setup needs admin consent for the Tempo app in your tenant. Clockwork, Toggl, Clockify Clockwork connects Outlook calendars on its Pro plan. Choosing an event and then an issue gives you a worklog prefilled with the meeting's time. Toggl Track and Clockify both show your Outlook calendar inside their apps, cloud Outlook only. Toggl can turn each meeting into a time entry on its own; Clockify has a "Copy as time entry" button. Those entries stay in Toggl or Clockify. Their Jira connections are browser extensions that add a timer button to the issue page, and there is no path from a calendar event to a Jira worklog. The Toggl community thread asking for exactly that has no answer. Planim Time on Microsoft 365 Planim Time is a time tracker for Jira on Windows, Mac and Linux. It connects to Microsoft 365 through the standard Microsoft sign-in with read-only calendar permission (Calendars.Read), and from then on your Outlook events, Teams meetings included, show up next to your worklogs: in a week calendar and at the bottom of each day's list. If the subject has an issue key, the meeting goes to that issue. When you choose an issue by hand, the app keeps the choice for the whole series and for meetings with the same subject, so recurring meetings stop asking. Anything left gets up to three keyword suggestions from your issues or falls to a default issue. Declined meetings, all-day events and slots marked free are skipped unless you turn them on. Each meeting logs with one click, and Log all logs the day. Events go from Microsoft Graph straight to your computer; the server only handles the sign-in. Private and confidential events are not read. The full walkthrough is in How to log meeting time in Jira straight from your calendar. What to decide before you connect anything Where ceremonies go. Standups and planning need an issue, because every Jira worklog does. Most teams keep one ceremonies issue per sprint and log topic meetings on the issue they were about. Decide that before you connect a tool, so logging a meeting doesn't start with working out where it goes. Who sees the meeting subjects. The subject of an internal meeting is often more sensitive than the hours. Read the privacy page of whatever you connect, and prefer tools that keep the events on your side.
This is a summary aggregated from Dev.to. Read the complete article on the original site:
Read full article at Dev.to