Description: The Rovo Dev usage dashboard shows 2,045/2,000 credits used (over limit), but the usage breakdown only accounts for 1,445 credits under "Code review in Bitbucket" — leaving approximately 600 credits unattributed to any capability.
Expected: All consumed credits should appear in the breakdown by capability.
Steps I reproduce:
Hi @Esty Shlomovitz,
Apologies for such a delay on our end! Thanks for flagging this - I've looked into it and want to share what's happening.
Good news first: Your credit tracking and billing are accurate. The total of 2,045 credits consumed is correct, and no credits have been lost or double-counted.
What's causing the confusion: This is a known display issue on the Your Usage page. The breakdown table currently only labels "Code review in Bitbucket" correctly. The ~600 unaccounted credits in your view are coming from two other Bitbucket capabilities that aren't being properly displayed:
Custom code reviews (~440 credits)
Acceptance criteria checks (~160 credits)
These features consumed credits as expected - they're just missing from the breakdown labels in the UI.
Workaround in the meantime: You can verify your accurate total usage in Admin Hub → Insights → Platform usage at http://admin.atlassian.com. This view reflects the same total (2,045) shown in the dashboard header.
On the overage: Your Rovo Dev Standard plan includes 2,000 credits per user per month, and usage beyond that is billed at $0.01 per credit. If you'd like to prevent future overages, your admin can configure a hard cap in Admin Hub.
Our engineering team has identified the root cause and a fix for the display is in progress however I cannot share any ETA on this one.
Best,
Anastasiia
Hi @Esty Shlomovitz - welcome to the Community,
we've seen multiple users reports issues with Rovo Dev credits in the past few weeks. Unfortunately, we can't do much from Community side of things.
I went ahead and escalated your question to the Atlassian Team.
You can also raise a Bug with the Rovo Dev Team directly: Submit a request or incident - Rovo Dev Feedback - Jira Service Management
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the quick response and for escalating this! I'll submit a bug report via the link you shared.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.