> ## Documentation Index > Fetch the complete documentation index at: https://helloluciallc.com/llms.txt > Use this file to discover all available pages before exploring further. # Log Issues Manually > File a maintenance issue on the manual page with no chat, and edit any saved draft there under the draft routing law. **Log Issues Manually** is the Fieldwork page for employees who would rather not log an issue through a conversation with Lucia. It is the same issue form the chat's review panel shows, hosted on a real page of its own at [luciafieldwork.ai/manual](https://luciafieldwork.ai/manual). It is also where every saved draft opens for editing. The founder's direction of 2026-08-25 (Manual logging gets its page, FILD-109): > This is NOT meant to be a modal. It is meant to be its own beautiful UX/UI for property > employees that do not want to log issues through AI chat. ## Get there * The drawer's **Log Issues Manually** row. * The **Rather type it in? Fill in the form** link under the chat composer. * The pen icon on any row in **Drafts**. * The address **/manual** directly; the page is deep-linkable, with ordinary back behavior. The hamburger menu and the page header stay present, so you can leave the way you leave any page. There is no ✕ trap and no overlay. ## Fill it in The page title is **Log Issues Manually**, with the line “A title and a photo are usually enough — everything else can wait.” The form is the one the chat's review panel uses; one implementation, two places. A title and a description. The title is required; the app says so in red only when it is actually missing. Take or add photos. The **Take photo** control sits in the amber family that marks a helper, not an error. Pick or add the location. While a newly typed location is still pending, an italic amber helper reads, in the founder's approved words: “Add or select a location to the maintenance issue or clear the location field before saving, sending, or submitting.” It is a helper, not an error (Location helper drops the red, FILD-160, 2026-09-01); it does block saving, sending, and submitting until you add the location or clear the field. Each shows **Select one** until you choose. Assigned to and estimated cost, both optional. A suggested name is not a dispatch and an estimate is not approved spend. Use the same send options and **Submit to Lucia** control as the chat path. A manually filed issue travels the same chain (the app → the Fieldwork API → the engine → the Maintenance Inbox) and becomes the same canonical record. No Lucia conversation is required anywhere. ## How the page reassures you * **Saving → Saved.** As you type, the indicator above the field, right-justified, shows “Saving…” from real unsaved-edit evidence and “Saved” only when the save has landed. Never a timer. On the served build this chip is the chat composer's own indicator, one component in both places (Manual save indicator matches chat, FILD-119, on `main` since 2026-09-08 and **In Review** pending the founder's phone proof). * **Per-field circles.** Each text field carries an empty grey circle that becomes a green circle with a check when that field's current content is durably saved. Green fires only on proven persistence; change the text and it returns to grey until the new content proves (Green circle checkmarks, FILD-144, founder-designed 2026-08-30). Priority and guest impact carry no circle; their **Select one** state already says it. * **Leaving keeps your work.** Leaving the page with content in the form silently saves it as a draft and returns the form clean, the founder-ratified “like magic” behavior of 2026-08-28. Reopen that draft and the details and photo are there. ## Start over On a fresh form that did not come from a chat and is not yet bound to a submitted item, a **Start over** control sits where the old dot-and-Saved word used to be, above the first field and right-justified. One tap arms it as **Clear everything?**; a second tap confirms. The form then regenerates through the Lucia Orbit loader and settles back empty, and no ghost draft appears later from the cleared content (Form clears and starts over, FILD-138, founder-placed 2026-08-30). Reduced-motion users get an instant clean form. The chat composer deliberately has no such button; **New** already clears it the right way, by saving first. ## Editing a draft: the draft routing law Every edit of a saved draft happens here. The founder's standing rule, recorded verbatim on Pen icon never reopens chat (FILD-156) on 2026-08-31: > Once a draft is durably saved to the actual Drafts list, clicking the pen icon to > re-open/edit the draft ALWAYS takes the user to the Log Issues Manually page. The pen icon > should never re-open a chat with Lucia on the same topic/issue. EVER. That holds for drafts born in chat and drafts born on this page alike. The chat's overlay review panel is for chat-born review in the moment only; once a draft is in the Drafts list, the form on this page is the edit path. Fixed on app `main` at `19676a5` and verified on the founder's phone on 2026-09-01 (“Ahhh, excellent design choice. I love it.”). Any exception requires his explicit yes. If a draft's fields cannot be bound when you open it, the form shows read-only with a plain note and a **Retry**, rather than opening a chat or claiming an edit it cannot keep. ## The manual page's tip The first time the page opens on an empty form, a tip titled **File it yourself** (“Fill in the details and submit — no chat needed.”) points at the first field. It closes with ✕, or when you scroll or start typing; **Replay the guides** brings it back. See [Tips and guides](/fieldwork/using-fieldwork/tips-and-guides). ## Status The page shipped on app `main` on 2026-08-25 and every behavior above is on the served build at `692a71c`. The two records that own it, Manual filing without the chat (FILD-31, the end-to-end filing) and Manual logging gets its page (FILD-109, the page itself), are both **Finalizing**: the founder approved one combined acceptance walkthrough on 2026-09-07, due 2026-09-11, and neither closes until he records it. This page does not report that walkthrough as passed. ## See also * [Log and track issues](/fieldwork/using-fieldwork/logging-and-tracking-issues) * [Tips and guides](/fieldwork/using-fieldwork/tips-and-guides) * [Owner review](/fieldwork/using-fieldwork/owner-review) ## Verification basis Verified on **September 10, 2026** against the app source at `692a71c`, the build the served bundle carried on that date, and the founder's words on the cited records. The route, doors, copy, Start over fence, per-field circles, and routing law are read from source; the walkthrough and the In Review save-indicator parity await the founder's proof.