Resolved-Without-Worklog by Project

A worklog entry is the primary evidence that work actually happened on an issue. When an issue is resolved without any worklog, it raises a simple question: was the work actually done, or was the issue closed to clear it from the sprint without completing it? This visual shows how many resolutions have no corresponding worklog per project.

What you can conclude

• A high proportion of unlogged resolutions in a project may indicate that time logging is not being enforced — either through culture or tooling.
• For compliance purposes, unlogged resolutions create audit gaps — there is no documented evidence of the effort that produced the resolution.
• A project with consistently high logged resolution rates is meeting its time-tracking compliance requirements.

How this chart works

Grouped bar chart showing resolved-with-worklog versus resolved-without-worklog per project. Use the date and project filters to focus on specific teams or periods.