Manual issues
Not everything worth tracking arrives in a log file. A manual issue lets you create an entry by hand - a bug you spotted, a feature request, or a task - and have it live in the same list as issues that Log Lens grouped from real events. It shares the workflow, tags, modules, severities, and history that automatic issues use, so you can triage everything in one place.
Kinds
Every manual issue has a kind. The default is issue.
| Kind | Meaning |
|---|---|
issue | A general problem to track |
bug | A defect |
feature_request | Something to build |
task | Work to be done |
Fields
Only a title is required. Everything else has a sensible default.
| Field | Rules / default |
|---|---|
title | Required, up to 500 characters |
description | Optional, up to 120,000 characters |
kind | One of the kinds above; default issue |
severity | A valid level; default INFO |
status | A valid workflow status; default open |
source_frame | Related source (e.g. a file), up to 1,000 characters |
environment | 1-100 characters; default local |
note | Creation note, up to 10,000 characters |
tag_ids | Array of existing tag IDs |
module_id | An existing module, or none |
Tag IDs and the module are validated - if any tag or the module does not exist in the current application, creation fails.
Zero occurrences
A manual issue starts with a count of 0. It has no underlying log lines, so there is no raw event to open and no occurrence timeline - it exists purely as a tracking record. The description (or the title, if you left the description blank) becomes its sample message.
Preserved on refresh
Each manual issue gets a unique, randomly generated fingerprint and is marked with a manual origin. Because that fingerprint never collides with real log events, ingestion and reindexing will never merge, overwrite, or delete it. Your hand-written issues stay put no matter how often you refresh or reprocess your logs.
Creating one also records a status-history entry (using your note, or a default line naming the kind) and runs your automatic tag rules against the new issue.