Skip to content

User guide

Zettra has three roles in a project. Viewers read. Members file, comment on and close tickets. Project admins also manage the tree, members, statuses, repositories and documents. A member can be limited to some clients; they then see only those clients' tickets and menus, and core work.

The module tree

Modules group menus, which are single screens or features, for example HR › Attendance › Overtime Approval. A menu can be specific to some clients.

Admins build the tree in three ways: - by hand, on the project's Modules tab, dragging nodes to reorder or move them; - from a CSV file (Modules → Import); - from a specification on the Documents tab (see below).

Each menu has a page showing its timeline, newest first with each decision record, and the behaviours in force for each client.

Tickets

Press c anywhere to file a ticket. It needs a title, a type, the client (or all clients for core work), who asked, and the menus it touches. A reason, saying why the client needs this, is what later answers "why".

  • Comments are Internal by default. Mark one Client-safe only when it may appear in a client-facing summary. Type @ to mention a member.
  • Links say that a ticket reverses, extends or relates to another. A reversing ticket supersedes the older decision.
  • The board moves tickets between statuses by drag and drop.
  • Live updates: the board, the ticket list and an open ticket follow changes made elsewhere, by a teammate, an AI agent or a Git commit, without a reload. While you are editing a ticket, it says "This ticket was updated" instead of changing under you, and refreshes when you save or cancel.
  • In the list, tick tickets to change their assignee, priority, due date, release or status together, or to Close out several at once: their decision records are drafted with AI one after another, then each opens in the close dialog to confirm or edit, and closing one opens the next.
  • Releases (project settings) such as v1.0 group the tickets that ship together; the board and list filter by them.
  • Client acceptance on a ticket records who at the client accepted the work, as in UAT sign-off, and when; the list filters on it and summaries show it.

Closing a ticket, by moving it to Done or Cancelled, opens the close dialog. It asks what changed, why, and what alternatives were rejected, prefilled from the ticket. Draft with AI fills these fields from the ticket's comments and linked commits. It leaves Why empty when the thread never says why, so you ask the requester instead of guessing. Nothing is saved until Close ticket.

Decision notes record decisions made in meetings, calls or emails, outside any ticket. They appear on menu pages and in Ask, and are cited like HRIS-DN7. A note about the whole project, such as a kickoff, needs no menu; whole-project summaries include it. A note's action items each become a ticket from its page, or all at once with Create all.

Ask

Open Ask from the top bar, a menu page or a ticket, and ask in Indonesian or English.

  • Chips above the question narrow the scope: project, menu, client, dates and person. Zettra also detects chips in the question.
  • Every claim ends with citation chips. Hover to see the source; click to open it. Sources can be tickets, decision notes (HRIS-DN7) and document sections (HRIS-DOC1/7.4).
  • When nothing in scope answers the question, Ask says "Not enough information" and shows the closest items instead of guessing.
  • Thumbs up or down tell admins which answers to improve.

Change summaries

On the project's Summaries tab: 1. Pick a module, a client, a closed-date range, a language and the audience. 2. Preview the closed tickets and notes by menu, and untick anything that should stay out. Unticked items are never sent to the model. 3. Generate. The summary is editable Markdown with cited bullets and an appendix of the items. 4. Print it (the browser saves A4 PDF), or copy it as Markdown.

Client-facing summaries use decision records and Client-safe comments only, and never Internal comments. A summary can also cover one release: its closed tickets, without decision notes.

Beside the summaries: - Weekly status lists what closed in the last 7 days, what is in progress, overdue, due in the next 7 days or without an assignee, for the whole project or one client, to print or copy into the client update. - Handover gathers, for every module and menu, its specification sections, the behaviours in force and what is still open, as one document to print or copy at the end of the project.

Finishing a project

When the work is done, a project admin archives the project from its settings. It becomes read-only for everyone and leaves the project pickers, Home and reminders, but stays readable under All projects; its admins can restore it from the banner on any of its pages.

Documents and tree drafts

Project admins upload a PDF, DOCX or Markdown specification on the Documents tab. The browser reads the file, and its headings become sections that Ask can cite.

Draft module tree proposes modules and menus from the document: - With AI on, the model reads it in the background, and the bell tells you when the draft is ready. - With AI off, the headings become the tree at once.

Review the draft: rename, retype, untick or add nodes. Every node shows the sections it came from, and nodes the tree already has are marked. Apply creates the ticked nodes and links them to their sections.

Code

Project admins connect GitHub, GitLab or Gitea repositories in project settings. Commits and merge requests that mention a ticket key such as HRIS-231 then show in the ticket's Code section, and Ask uses them as evidence. A pushed commit that says Fixes HRIS-231 (or closes, resolves) moves the open ticket to In review, the project's last working status; closing it stays with you, since it needs the decision record.

Notifications

The bell shows assignments, comments, mentions, status changes and finished imports or tree drafts, live while the app is open. Each morning from 08:00 in your timezone it also reminds you of your open tickets due today or tomorrow, and of those that went overdue yesterday. Your profile turns each event on or off, and can turn on browser notifications, and, once your admin has set up email, an email of what you have not read after a couple of minutes.

For scripts

Personal API tokens (Settings → API tokens) call the same REST API as the app, read-only or read-write. The API is described in api/openapi.yaml.