Visionality for Atlassian · Work tracking + source control
Every AI dollar tagged to a Jira epic, a Bitbucket repo, and an end-customer.
Software-services shops billing time-and-materials need AI cost attribution that survives a client audit. The Jira epic identifies the work; the Bitbucket repo identifies the codebase; the end-customer identifies who pays. Visionality is the only AI Control Plane that connects all three to every API call automatically.
The Jira connector + Bitbucket connector together produce the metadata Visionality needs to auto-tag every IDE, Copilot, Cursor, and Claude API call. The chargeback CSV at month-end is per-Jira-epic, per-Bitbucket-repo, per-engineer, per-end-customer. The case study customer for this flow is ArcTrade.
What Visionality does for Atlassian
Tagged, governed, audited — at the call, not after the bill.
Bitbucket connector — workspace repos + Pipelines billing.
Pulls Bitbucket Cloud workspace repos with Jira project_key embedded; emits repo metadata events. Optional Pipelines build-minute overage billing.
Jira connector — projects + epics + categories + lead.
Pulls Jira Cloud projects with full metadata (key, name, lead, project type, category, archived flag) for downstream attribution. Self-hosted Jira Data Center supported.
Repo → Jira project mapping inherited from Bitbucket.
Bitbucket's native Jira-link embeds project_key on every repo. Visionality reads it automatically; operator confirms the mapping in the dashboard; from then on every IDE call carries the right project_id with no engineer involvement.
Chargeback CSV as time-and-materials invoice appendix.
Per-Jira-epic, per-Bitbucket-repo, per-engineer cost rows ready to drop into your client invoice as an evidence appendix. Drives ArcTrade's per-customer billing.
Govern your Atlassian AI spend in 30 minutes.
30-minute deploy. Bring your own LLM keys. Your existing SDK code works unchanged. The Atlassian connector is shipped — operator wires credentials and you have a working audit trail before the coffee is gone.