mark_issue
Ignore, acknowledge, or reopen tracked issues
Overview
Change the status of a tracked issue. Use this to acknowledge issues you've seen, ignore issues that don't matter (like WordPress rendering artifacts), or reopen issues that were prematurely resolved. This keeps your issue list clean and focused on what actually needs fixing.
How It Works
- Takes an issue ID and an action (ignore, acknowledge, or reopen).
- Updates the issue status in the database.
- Ignored issues won't appear in future comparison reports.
- Reopened issues are marked as 'detected' again and will be tracked in subsequent comparisons.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
issue_id |
string |
required | Issue ID (e.g. ISS-abc123) |
action |
ignore | acknowledge | reopen |
required | Action to take on the issue |
reason |
string |
optional | Reason for ignoring (required when action is 'ignore') |
What You Get Back
- Updated issue status
- Confirmation of the action taken
Example Use Case
After comparing pages, you notice several issues flagged as 'wp_artifact' — differences caused by WordPress plugin markup that won't exist in your React clone. Mark them as ignored with a reason, so they don't clutter your fix list.
Tips
Use 'ignore' for WordPress artifacts, plugin-specific markup, and intentional design changes.
Always provide a reason when ignoring — it helps with audit trails.
Use 'reopen' if a resolved issue reappears after further changes.
Acknowledged issues remain tracked but signal that you've reviewed them.