Resolved-Without-Worklog Trend(JIRA:4.5.10)

Visual

An issue resolved without a worklog has no recorded time behind it: Jira holds no worklog entry for the effort spent on it. This visual shows, for each week, how many issues were resolved and how many of them have no worklog, across the selected projects.

What you can conclude

  • A without-worklog line that runs close to the resolved line, week after week, shows that most resolutions carry no recorded time; a reviewer could ask whether the teams concerned log time in Jira at all.
  • A week in which the without-worklog line rises while resolutions hold level shows more resolutions without recorded time that week; the question it raises is what changed in how time was recorded.
  • For a review, an unlogged resolution is one with no recorded time in Jira; whether the work behind it was done is not in the data.

How this chart works

Two lines, one point per week: the issues resolved that week, and those among them with no worklog. An issue counts as resolved when it moves into a status of Jira's Done category that counts as delivered under your organization's terminal-status settings (a MetaFrazo default applies until configured). A move into a status classified as abandoned is not counted, because an abandoned issue ended without delivery. An issue counts as without a worklog when no worklog entry is recorded on it at any time, so a worklog added later moves an earlier week's resolution from without to with. An issue resolved in two different weeks counts in each. These are the resolutions Resolved-Without-Worklog by Project counts, so over the same dates the weeks add up to that chart's totals and to the Unlogged resolutions card.

A week in which the selected projects recorded activity but no resolution is drawn at a measured 0. A week in which nothing was recorded for them draws no point and the lines break there, because no data is not the same as zero. Hover a week to see its counts and the share without a worklog, the without-worklog count over the resolved issues, to one decimal; a week with fewer than five resolved issues shows its counts and no share.

The week in progress is shown at its value so far. Because the week is not yet complete, it covers only the resolutions recorded so far and can move in either direction as the week closes.

What Deep Analysis reads

Deep Analysis reads each complete week's counts added up over the selected projects, with the share without a worklog for every week that resolved at least five issues. The week in progress is left out of its figures, because its counts are partial.

How far back it reads

The chart reads the same dates as Resolved-Without-Worklog by Project: at most the last 92 days, a calendar quarter, of the selected range, ending on the range's last day or today, whichever is earlier. A range that starts within those 92 days is read whole. For a longer range, or one with no start date, it covers the weeks of those 92 days, and the panel says so beside its title. To review an earlier period, end the range there.