Concepts

Concepts

Organization, project, status workflow, roles, severity, hours and documents.

  • Organization: the client company. One organization's data never shows up in another.
  • Platform: the Aquarela team that runs tracker. The platform owner defines what each person sees or manages (companies, support, invites, AI credits, log); a suspended company has no access until it's reactivated.
  • Beta: tracker is in beta, with invite-only access. The platform team generates the beta invite (create_beta_invite, POST /beta-invites); whoever uses it creates their account and their own company, and the invite records who invited whom.
  • Project: has a prefix (e.g. MOB) used in issue codes (MOB-0001), and its own issue types, labels, modules and custom fields.
  • Status workflow: each project has its own statuses, each in a group (todo, in_progress, done), with the roles that can move issues into it and the statuses it can come from. Projects start on the Software + QA template (Triage, To do, Doing, In review, Testing, Done, Canceled), the Software template (To do, Doing, In review, Done) or the QA template (Draft, Open, Triage, Prioritized, In development, Ready for QA, Retesting, Approved, Failed, Completed and Closed). "Open" means everything that isn't in the done group.
  • Retest: QA records the result with version and device. In Software + QA, passing moves it to Done and failing sends it back to To do with the failed flag (retest_failed), until it passes; in the QA template, it goes to Approved or Failed.
  • Closed (QA template): a single status for what closes without being resolved, with the reason (close_reason: duplicated, canceled, not reproduced or won't fix).
  • Blocked: a flag on the issue, with the reason, that works in any status and workflow (it isn't a column). Filter with blocked_only or bloqueio = sim in the advanced query.
  • Projects created before these workflows keep their old statuses (Retesting, Approved, Failed, Blocked, Reopened, Duplicate...) until someone asks to "Simplify the workflow" in Settings > Status workflow.
  • Severity: S1 (critical) to S4 (low), technical impact. Priority: urgent, high, medium, low, business importance.
  • Hours: each issue has an estimate, a start and a due date, and time entries (who, day, how much, what they did). Remaining = estimate minus what's logged. Duration as text: "2h", "1h30", "45m", "1d" (8 h).
  • Documents: the company's knowledge base (manuals, business rules, FAQs, processes), in markdown, for the whole company or one project. A draft (draft) is seen only by those who edit; internal is for the team (admins and the project's PO/PM, QA or dev; stakeholders don't see it) and for agents connected on their behalf; public also shows up in the company's public help center, which has its own llms.txt (and llms-full.txt, with all the texts) for chatbots and RAG without signing in. Search (search_docs, GET /docs/search) returns passages per section, accent-insensitive.