Issues

Issues are the results generated by a Maintain run with one or more enabled rules. Each issue represents a specific violation, risk, or code quality concern found in the codebase. They help teams improve correctness, reliability, security, and maintainability across the project.

Issue attributes

Each issue in Artemis includes the following details:

• Rule The rule that triggered the issue (e.g., Error and Exception Handling).

• Severity Indicates how serious the issue is if left unresolved:

  • Critical (9.0-10.0): May cause crashes, severe security risks, or data loss.
  • High (7.0-8.9): Major functional or security risks.
  • Medium (4.0-6.9): Moderate impact; could affect maintainability or stability.
  • Low (0.1-3.9): Minor or stylistic issues, non-blocking.

• Difficulty to Fix Estimates the effort required to resolve the issue:

  • Easy (0.0-4.9)
  • Medium (5.0-7.9)
  • Hard (8.0-10.0)

• Location Displays the file path and line number where the issue was found.

• Description Explains the cause of the issue and its potential impact.

• Fix Button Provides an actionable recommendation or an automated fix powered by Artemis.

Step 1: Detect issues

Enable one or more rules and run a scan from the Rules or Issues panel to detect issues. If you have not defined or enabled any rules yet, refer to the Rules section.

Step 2: Review the issue list

Once the run is complete, the issue board shows the current state of every finding:

The board groups findings by condition so you can review them at a glance:

• Untriaged for newly detected issues
• Triaged for findings that have been reviewed
• In Progress for issues currently being worked on
• Done for completed or resolved issues

Step 3: Review details and fix

Click on any issue to view detailed information and available fix options.

In the review flow, the user can mark a finding as a false positive or confirm it as a real issue. Confirming the finding approves the change so the workflow can continue.

Step 4: Review the changeset and create a PR

After Artemis generates a fix, open the associated changeset from the issue detail view. Review the proposed code changes, confirm that the diff matches the issue, and then create a pull request when the changes are ready for team review.

Benefits of issue detection

• Prioritization - Severity and difficulty scores help teams focus on high-risk, easy-to-fix issues first.
• Visibility - Developers can quickly locate and understand problems in the codebase.
• Continuous improvement - Regular maintenance runs help keep code quality and project stability consistent over time.