Skip to main content

Create a manual issue, bug, or task

Not every problem starts as a log line. Use manual issues to track bugs you found by hand, feature requests, or tasks alongside your ingested errors. They live in the same list, take the same workflow status, and accept the same tags as automatically detected issues.

From the UI​

Open the issue list and choose New issue. Fill in a title, pick a kind and severity, optionally attach a module and tags, then save. The new item appears immediately with an occurrence count of 0.

From the API​

Send a POST to /?api=issues. Only title is required.

curl -X POST "http://localhost:8080/?api=issues" \
  -H "Content-Type: application/json" \
  -H "X-Log-Lens-Token: your-key" \
  -d '{
    "title": "Checkout button unresponsive on mobile",
    "kind": "bug",
    "severity": "ERROR",
    "status": "open",
    "module_id": 3,
    "tag_ids": [1, 5],
    "description": "Steps to reproduce...",
    "environment": "production",
    "note": "Reported by QA"
  }'

You can also send the key as Authorization: Bearer your-key.

Fields​

FieldDefaultRules
title-Required, max 500 chars
kindissueOne of issue, bug, feature_request, task
severityINFOEMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG
statusopenopen, in_progress, fixed, wont_fix, reoccurred
description-Max 120,000 chars
source_frame-Related file/location, max 1,000 chars
environmentlocal1-100 chars
module_idnullMust be an existing module in this application
tag_ids[]Array of existing tag IDs
note-Creation note, max 10,000 chars

What happens on save​

  • The issue gets a unique fingerprint, so it never merges with an ingested issue.
  • Its origin, channel, and log type are all recorded as manual.
  • A status-history entry is written. If you omit note, it defaults to Created manually as <kind>.
  • Automatic tag rules run, so matching rules may add more tags.

A successful call returns the newly created issue (HTTP 201), including its ID.