Align Bitbucket Pipelines usage period with Admin Hub billing entitlement period

XMLWordPrintable

    • 1

      Problem:

      Customers report different build minute totals between the two official usage views, even when reviewing what appears to be the same monthly period:

      • Bitbucket > Workspace settings > Pipelines > Usage details
      • Atlassian Administration > Usage > Meters > Bitbucket build minutes and Billing > Entitlements

      Investigation shows both totals are correct against their own window. The difference is caused by different monthly anchors:

      • The Bitbucket in-product view tracks an operational cycle anchored to the workspace creation date.
      • Administration tracks the commercial billing cycle anchored to the organization billing account recharge date managed by the central Commerce platform.

      When those two anchors fall on different days of the month, for example a 2-day offset, builds that run in the gap are included in the current cycle in one view but were counted toward the previous billing period in the other view. There is no Admin Hub setting and no support operations procedure to manually shift either anchor to align them.

      This is a known scenario reviewed with the Commerce and Usage platform teams as part of ongoing work to unify usage reporting onto a single billing period source of truth.

      Impact:

      • Confusion when reconciling usage against the monthly plan allowance
      • Additional support investigation to explain why two official views show different totals
      • Difficulty validating invoicing and limit consumption

      Current behavior:

      • Bitbucket Pipelines usage details uses the workspace operational cycle based on the workspace anchor date.
      • Administration > Usage > Meters uses the subscription allowance recharge date and billing period from the billing entitlement.

      Expected behavior:

      Unify both views onto the same billing period so customers see consistent totals:

      1. Have Bitbucket Pipelines usage details display and calculate against the Commerce billing entitlement period by default, using the recharge date as the anchor for Current period and Usage resets on date.
      2. Or, surface both periods clearly in the UI with an explanatory note and a toggle: View by Workspace operational cycle vs View by Billing period. 
      3. Ensure totals for the same selected billing period match across Bitbucket and Administration after ingestion delay is accounted for.

      Acceptance Criteria:

      • When a workspace is linked to a billing entitlement, Pipelines usage details shows the same Current period dates as Administration > Usage > Meters > Bitbucket build minutes.
      • Totals for the same selected billing period match across both locations.
      • The reset date is consistent across both pages.

      Workaround today:

      Use Atlassian Administration > Usage > Meters > Bitbucket build minutes as the source of truth for plan allowance and invoicing. For granular build investigation, filter Bitbucket Pipelines usage details to the exact billing period dates shown in Administration to reconcile the totals.

              Assignee:
              Unassigned
              Reporter:
              Jairo O
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: