Tickets get a creator and an assignee; the inbox shows what is assigned to you

History

1. Architect opened the ticket 2026-09-25 10:23
2. AntColonyScheduler changed the state progress 2026-09-25 10:24

   A worker started on this ticket.

   colony-lease: s-20260925T0824-14c8bc · host Loreana · started · ms 1790331884898

3. AntColonyScheduler commented 2026-09-25 10:28

   Built — goes live with the next deploy.

   colony-report: s-20260925T0824-14c8bc · sha256 9aae872b656b · controller pass · ready to deploy

4. Architect edited the ticket 2026-09-25 10:46

   Subject before: Answering a ticket without confirming it

   Summary before

   When the creator comments on a ticket that is waiting for him, it goes back to whoever asked: new state "answered", out of his inbox. No need to confirm just to answer. Test:

   1. Open a ticket in "awaiting creator", write a comment as the creator: it shows "answered" and is gone from the inbox.
   2. The asker comments back and sets "awaiting creator": it is in the inbox again. Details: "confirmed" stays "tested, works". The scheduler/librarian treat "answered" like an answer (DECISIONS.md). Architect's proposal. Creator: "it feels weird to set a ticket to confirmed when i just answer or have another question".
5. Architect changed the state open 2026-09-25 10:46

   Redesigned by the creator in chat (see the new text); the first build (state "answered") is not deployed — rework it to this.

6. AntColonyScheduler changed the state progress 2026-09-25 10:46

   A worker started on this ticket.

   colony-lease: s-20260925T0846-2af081 · host Loreana · started · ms 1790333201931

7. AntColonyScheduler commented 2026-09-25 10:47

   Paused: the scheduler was stopped — work continues after 2026-09-25 08:47 UTC.

   colony-parked: s-20260925T0846-2af081 · host Loreana · phase worker · resume-ms 1790326045662 · ms 1790333245662

8. Architect edited the ticket 2026-09-25 10:47

   Subject before: Tickets wait for a person; each inbox shows what waits for you

   Summary before

   A waiting ticket names who it waits for ("waiting for Caramboleyo"). Each user's Inbox (and its badge) shows only the tickets waiting for them. When that person comments, the ticket waits for the one who asked instead and leaves their inbox — no need to confirm just to answer. Test:

   1. As Architect, set a ticket waiting for Caramboleyo: it is in Caramboleyo's inbox, not in Architect's.
   2. As Caramboleyo, comment on it: it now waits for Architect — gone from his inbox, in Architect's.
   3. Log in as another user: the inbox shows only their own items. Details: replaces the "answered" state built first (not deployed). "awaiting creator" keeps working as "waiting for the creator" so the scheduler and Anton don't break. Confirm/reject stay the creator's. Creator: "it feels weird to set a ticket to confirmed when i just answer or have another question", "maybe add a status pending? but then the scheduler or another user would not know its waiting for them", "shouldnt you see items waiting for you?"
9. Architect changed the state open 2026-09-25 10:47

   Creator in chat: "we probably need to add creator and assignee" — text updated; the parked session is dropped, start fresh from this.

10. AntColonyScheduler changed the state progress 2026-09-25 10:47

    A worker started on this ticket.

    colony-lease: s-20260925T0847-af6abd · host Loreana · started · ms 1790333263784

11. AntColonyScheduler commented 2026-09-25 10:49

    Paused: the scheduler was stopped — work continues after 2026-09-25 08:49 UTC.

    colony-parked: s-20260925T0847-af6abd · host Loreana · phase worker · resume-ms 1790326173895 · ms 1790333373895

12. Architect changed the state pending 2026-09-25 10:49

    Stopped: the creator is still discussing what to build. The text above is only a draft; nothing gets built until he decides.

13. Architect commented 2026-09-26 09:25

    Superseded by https://tickets.worldapi.org/projects/tickets.worldapi.org/20 (projects, members, roles, created by + assigned to, per-person inbox).