Menu

1 / 2

How to track meeting time in Jira (and see how much of the sprint it eats)

DEV Community: productivity·Vladimir Letiagin·14 days ago
#E4vrOw8X
#devtoproductivity#devto#dev#meeting#issue
Reading 0:00
15s threshold

Every few months someone asks Atlassian Community how to track meeting time in Jira, and the thread fills with the same three answers. Jira has no notion of a meeting. Time exists only as worklogs, and a worklog must belong to an issue. So meeting time either gets an issue to live on, or it quietly disappears and the sprint looks like it had five more productive days than it did. Where to log it is the first half of this. The second half is reading the number and letting Planim Time fill it in from your calendar.

Three places meeting time can live

A ceremonies issue per sprint. Create OPS-15 Sprint 42 ceremonies with the sprint, and standups, planning, refinement and retro all get logged there. The point is the report: at the end of the sprint the issue's time spent is your ceremony cost, one number, comparable sprint to sprint. Some teams make it one issue per quarter instead; the per-sprint version is easier to compare.

The issue the meeting was about.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.