Skip to end of banner
Go to start of banner

Time in Status Report

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

About

This report shows how long a set of issues spent, on average, within a given set of statuses, plotted against the date the issue was created. Equivalent statuses can be placed in the same group to be combined and plotted in the same series. At least one status group (containing at least one status) must be supplied, and statuses may not be duplicated within groups. More than one status group can be specified to show multiple series on the same chart. Results are shown as the average number of hours that statuses spent within the group over their lifetime.

To report on the actual transition times (instead of the total time spent in the status), see also the Time from Status to Status Report and Time to Next Status Report reports.

Common Uses

This report can be used to show how long a set of issues spent in a development queue or in QA. For example, if your workflow includes two statuses to show time spent in (or waiting for) QA, such as "Awaiting QA" and "In Test", both of these statuses could be added to the first status group in order to show the total average time spent in any of the QA statuses. To show time spent in development as a second series on the same chart, statuses such as "In Progress" can be added to the second status group.

The time reports use the 24-hour clock.

When reporting time in units of hours, only the sum of hours is shown, irrespective of whether the hours are distributed across non-workdays or non-work hours.

For example, if the total hours amount to 36 hours, the calendar displays 36 hours and not 4.5 days, which would be 108 hours with the 24-hour clock, because each work day is eight work hours.

Page Contents

  • No labels