The Scenario
You are a QA lead. The payments-service repo has been going through a major refactor and you need to show the engineering director whether the vulnerability count is trending down over the last 10 commits to main. Bitbucket stores code-quality report annotations on each commit — vulnerability count, coverage percentage, severity, and the file path where each issue was found.
The data is attached to each commit in Bitbucket's Reports tab. Getting it into an Excel workbook for trend analysis means opening each commit's report page, reading the annotations, and pasting rows. Ten commits, multiple annotations each.
The bad version of this week:
- You open commit one in Bitbucket, navigate to Reports, read the annotations, paste a row into Excel
- You open commit two and repeat
- By commit five you realize some commits have multiple reports from different scanners (SAST, coverage, lint) and you are not sure which rows belong to which tool
- By commit eight the data is in the workbook but column order differs between commits because you clicked in different sequences
- The trend chart you build is wrong because commits six and seven have the wrong severity mapping.
The fast version is one prompt.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent inside your Excel workbook that fetches commit reports and annotations via the Bitbucket API, handles the multi-report-per-commit structure, and writes a clean trend-ready dataset in one pass.
Open the SheetXAI sidebar and type:
For the last 10 commits on the main branch of Bitbucket repo 'payments-service' in workspace 'acme-corp', fetch all commit report annotations. Write commit hash, commit date, report type, annotation severity, file path, and annotation message into columns A through F of the Annotations tab. One row per annotation.
SheetXAI fetches the commit list, pulls all report annotations for each commit, and writes the flat table with consistent column ordering across all ten commits.
What You Get
A flat annotation log with one row per finding:
- Commit hash — which commit the annotation belongs to
- Commit date — for sorting the trend chronologically
- Report type — SAST, coverage, lint, or whatever tools ran
- Severity — critical, high, medium, low, or info
- File path — where the issue was found
- Message — the annotation description
Consistent column order across all commits. No copy-paste mismatches from clicking in different sequences on different commit pages.
What If the Data Is Not Quite Ready
Code-quality annotation data from Bitbucket has edge cases in real QA workbooks.
When you only want vulnerability-type annotations
The trend analysis is about security vulnerabilities, not code style or coverage.
For the last 10 commits on the main branch of Bitbucket repo 'payments-service' in workspace 'acme-corp', fetch all commit report annotations. Filter to annotation type 'VULNERABILITY'. Write commit hash, commit date, severity, file path, and message in columns A through E of the Annotations tab.
When you need per-commit vulnerability counts for the trend chart
The raw log is useful for drilling in, but the chart needs one row per commit with totals.
For the last 10 commits on the main branch of Bitbucket repo 'payments-service' in workspace 'acme-corp', fetch all commit report annotations of type 'VULNERABILITY'. Write the full annotation log on the Raw tab. On the Trend tab, write commit hash, commit date, total VULNERABILITY annotation count, and CRITICAL severity count per commit, sorted chronologically.
When some commits have no reports and need to appear as zero-count rows
Not every commit triggers a full scan. You want those represented in the trend with a zero count rather than a gap.
For the last 10 commits on the main branch of Bitbucket repo 'payments-service' in workspace 'acme-corp', fetch all commit report annotations. On the Trend tab, write one row per commit even if it has zero annotations. Write commit hash, commit date, and annotation count (0 if none), sorted chronologically.
When the director wants vulnerability count and coverage percentage trending together
The director wants both security posture and test coverage in one view.
For the last 10 commits on the main branch of Bitbucket repo 'payments-service' in workspace 'acme-corp', fetch all commit reports and annotations. Write the full annotation log on the Raw tab. On the Trend tab, write one row per commit showing commit hash, commit date, VULNERABILITY annotation count, CRITICAL annotation count, and coverage percentage from the coverage report. Sort chronologically.
The pattern: the annotation log and the trend chart data both come from one prompt. The director gets the drill-down view and the trend overview without a second pass through Bitbucket.
Try It
Get the 7-day free trial of SheetXAI and ask it to pull code-quality report annotations from any Bitbucket repo into a blank Excel workbook. The Bitbucket integration is included in every SheetXAI plan. For related workflows, see how to analyze pipeline run reliability in Excel or the Bitbucket in Excel overview.