Skip to main content

Introduction to Buckets

Written by George Mihailov

Buckets are used for comprehensive time spent reporting. There are two reporting options: by category and simple.

Buckets: reporting by categories

Reporting by categories allows slicing the total time spent between multiple categories. For example, costs analysis categories can be:

  • New Features

  • Existing Features

  • Internal Systems

  • Onboarding

  • Professional Services

  • Tech Debt

As you categorize items, Quantify will start suggesting a category for new items. Suggestions are scoped per bucket, or in other words, are based on the categorized items within the Bucket.

Buckets: simple reporting

Simple reporting uses JQL (Jira Query Language) to report time spent based on the items returned by the query.

Bucket Lifecycle

Each Bucket has a start date and end date. We recommend creating one bucket per calendar or fiscal year. This allows you to archive past reports in read-only mode for record-keeping purposes.

Similarly, every reporting period (month/quarter) can be closed to ensure that the reported numbers don't change.

Keeping a bucket up to date

An open period is a copy of the tracked hours taken when the period was built. Later changes to the underlying data, such as imported time off, corrected timesheets or new activity, do not flow into the bucket automatically.

To bring a bucket back in line, expand the Updates card in the scope manager. It lists the people whose hours differ from the bucket. Apply the update per person or use Update All, then export again. Closed periods are frozen by design; reopen a period first if it needs to be updated.

Did this answer your question?