Create Tracking Issues

Track it now. Fix it when it fits. Turn the review findings you choose into Jira tickets, GitHub issues, or GitLab issues, with an optional assignee and note, and see which ones are already tracked.

Book a demo All use cases

From finding to ticket, evidence attached.

Turn selected findings from the last review into Jira tickets, GitHub issues, or GitLab issues, with an optional assignee and note. Returns ticket links and identifies findings already tracked in the same session.

Claude Code/cloudaeye:create-issue [2,4] jira Jane Doe

From the last review

  1. 1The retry loop allows one attempt more than RETRY_CAP.Highpayments/retry.ts:41
  2. 2Calls Invoice.recalculate_totals(), which is not defined anywhere.Mediumsrc/billing/invoice.py:88 · hallucinated_api
  3. 3A negative RETRY_CAP is accepted.Mediumpayments/config.ts:18
  4. 4Unused import: decimal.ROUND_UP.Lowsrc/billing/refund.py:3 · dead_code

AgentFile findings 2 and 4 as Jira tickets assigned to Jane Doe? YouYes.

Result

FiledPROJ-5311

2. Calls Invoice.recalculate_totals(), which is not defined anywhere.

File, line, severity, and evidence in the ticket body. Assigned to Jane Doe.
Already filedPROJ-5298

4. Unused import: decimal.ROUND_UP.

Filed earlier this session, so it is not filed twice.

Not every finding
belongs in this PR.

Some findings are worth fixing, just not now. File them where your team already tracks work, with the evidence attached, so they do not get lost.

For findings you won't fix in this change.

The pre-existing bug next to your edit, the medium-severity item the release cannot wait for, or the issue another team owns.

  • Pre-existing bugFound beside your edit
  • Not urgentPlanned for later
  • Another team's codeRouted to them
See an example

Jira, GitHub, or GitLab, with an assignee.

File to Jira, or as a GitHub or GitLab issue. Add an assignee if you want one, and a note that goes at the top of the ticket.

  • JiraAssignee by display name
  • GitHub and GitLabAssignee by username
  • Your noteTop of the ticket
See the commands

Safe to re-run.

Findings already filed this session are matched by their content, not their number, so a re-review that renumbers findings never files one twice.

  • Matched byPath and title
  • Already filedExisting ticket named
  • After a re-reviewNo duplicates
Read the docs

Real tickets, confirmed first.

Tickets get an assignee and land on a board, so your agent confirms before filing and never assumes who should own one.

  • Before filingAsks you to confirm
  • "File them all"Confirms the count first
  • AssigneeNever assumed
Explore Bug Review

Commands

Claude Code
/cloudaeye:create-issue [2] jira Jane Doe
Codex
$cloudaeye:create-issue [1,3] github octocat
GitHub · Bitbucket · GitLab
@cloudaeye /create_issue jira Jane Doe

On a pull request, post it as a reply to the CloudAEye review comment you want to track.