Skip to main content

Issues

An Issue is a finding a Scan recorded against a Rule and a code location. It can be a real problem or a false positive, so it needs triage before anyone fixes it. An Issue is different from a Task in a Plan and from a ticket on your Git provider.

What an Issue shows​

  • Rule: the Rule that raised it.
  • Severity: Critical, High, Medium, Low or Info.
  • Confidence: how sure the scanning agent is about the finding.
  • Complexity of fix: an estimate of how big the fix is.
  • File and Lines: where the finding is, with the code shown alongside. View full file opens the whole file.
  • Details: what is wrong and why it matters.
  • Fix history: every attempt at fixing it, with its agent log and Branch.

Explain issue asks the agent to walk you through the finding.

The Issues board​

The board has four lanes:

  • Untriaged: new findings from a Scan.
  • Triaged: findings you have reviewed.
  • In Progress: Issues being fixed.
  • Done: fixed Issues.

Switch between the board, list and file views, group and sort the Issues, and filter by Rule, severity, confidence, complexity of fix or sync status. Archived Issues have their own view.

Triage​

For each Issue, Confirm it as a real problem or mark it as a False positive. Archive removes an Issue from the active board without saying it was fixed. You can select several Issues and act on them together.

Issue validity, fix progress and whether the finding still matches the code are separate. When the code changes, an Issue can become outdated or obsolete. Resync checks it against the current code, and the resync action on the Maintain page checks every outdated Issue at once.

Fix​

Pick the route that suits the Issue:

  • Fix sends it to a coding agent, which proposes the change on a Branch. Select several Issues to fix them together.
  • Fix in Discovery hands a complex Issue to a Discovery Run, which tries several approaches and measures them.
  • Plan a fix writes a Plan with Tasks before any code changes.
  • Copy for local agent copies the full Issue as Markdown to paste into your own coding agent. With the Artemis CLI, your agent can send its fix back to the Issue with artemis maintain issues submit-local-fix, so the board keeps the record.

A completed Fix does not mean the change was published or merged. Open its Branch with View branch, verify it on the Scripts tab, then publish it or open a Pull Request. See Branches.

Last updated on by Eoin