Documentation

Quick start

1. Install Rovo & Usage Cost Center on the Jira Cloud site where your team groups live (requires Jira admin access).
2. Open Jira Settings → Apps → Rovo & Usage Cost Center.
3. Export the Rovo credits CSV from Atlassian Administration (steps below) and drop it on the Import tab.
4. Map teams via Jira groups or a CSV mapping file, set rates and allowances in Settings, then review Overview, Budgets, and Exports.

How to export the Platform usage CSV

You must be an organization admin. The only documented usage export today is Rovo credits.

1. Open admin.atlassian.com and select your organization.
2. Go to Insights → Platform usage.
3. Select Rovo credits, then Export data.
4. Atlassian prepares the file asynchronously and emails you when it is ready. Download from the email link (the link expires after 24 hours).
5. In the app, open the Import tab and drop the downloaded .csv. Do not edit it in Excel first — Excel can re-encode the file and reformat dates.

The export covers up to about 3 months of usage or the first 1 million usage events, whichever limit is reached first. Import regularly so history stays available beyond that window. Consecutive exports overlap; the app deduplicates by day.

Older tenants may still show Settings → Platform usage instead of Insights. Use whichever path your admin console shows.

Team mapping file format

Upload a CSV on the Teams tab (or Settings) with columns:

user,team,cost_center
712020:23b8c1e9-3924-56de-3eb1-3b9046685257,Platform,CC-100
alice@example.com,Engineering,CC-200

• user — Atlassian account ID or email (or display name; display-name matches are treated as weak).
• team — team name used for attribution and chargeback.
• cost_center — optional cost centre label for finance exports.

Uploading a mapping file replaces the previous mapping. Preview shows unmatched rows before you confirm. You can also assign teams from Jira groups (priority-ordered). Precedence: mapping file → group rules → No team.

Budgets and forecasts

• Set a monthly credit budget per team and optionally an org-wide budget in Settings.
• Default alert thresholds are 80% (warn) and 100% (critical); both are configurable.
• The Budgets tab shows month-to-date usage, month-end forecast, and first-crossed history. Alerts appear in-app only (no email).
• Overview forecasts month-end usage against your configured allowance using weekday/weekend run rates from imported daily totals.

Attribution cleanup rules (ROVO-1265)

Atlassian’s Platform usage export intermittently leaves Feature and Agents blank for some usage events (ROVO-1265). That is an Atlassian export issue, not an app error. Those rows land in an explicit Unattributed bucket.

On the Attribution cleanup tab you can define ordered, versioned rules such as: when Feature and Agent are blank and the user (or team) matches X → attribute to feature Z / agent Y / team T. Rules apply only at report time; stored day and period totals are never rewritten. Preview before applying. Chargeback CSV/PDF mark export vs cleanup_rule attribution.

Chargeback exports

On the Exports tab you can download:

• Team CSV — one row per team for the period (credits, share, allocated cost, attribution source).
• Detailed team CSV — one row per team and attribution source (export vs each cleanup rule) for audit.
• User CSV — per-user detail with team and cost centre.
• PDF — cover summary, team table, top agents, data-quality note, and disclaimer.

All CSVs are UTF-8 with BOM for Excel. Manual org-level meters (for example automation steps entered by hand) appear on the Usage bill; team chargeback remains Rovo-credits based.

Other meters

Automation steps and similar meters do not have a documented Platform usage CSV today. Enter period totals manually on the Usage bill tab and set rates in Settings.

Privacy and security

• Forge-native; Runs on Atlassian — no egress, data stays in Forge storage on your site.
• CSV is parsed in the browser; only aggregated totals are stored.
• Never collects Atlassian API tokens or passwords.
• Scopes: storage:app, read:group:jira, read:user:jira, read:avatar:jira, report:personal-data.
• Stored Atlassian account IDs are reported via Atlassian’s personal data reporting API; closed accounts are anonymised.

See the Rovo Cost Center Privacy Policy and EULA.

Support

Email support@clearstepsapps.com. Include your Atlassian site URL and a short description of the issue. For security concerns, use security@clearstepsapps.com.