FixControl/Documentation

User Guide

Action items

Concrete follow-up steps per issue, generated by the Operations Coordinator — different per kind of work.

What action items are

Action items are the concrete follow-up steps queued up for each issue. They are produced by the Operations Coordinator (an agent) and live on every issue detail page. You tick them off, start them, or remove them. Nothing executes automatically — the list is your checklist.

Issue detail page with action items
Issue detail page with action items

Per kind: SUPPORT, BUG, FEATURE

The contents of the list depend on the issue kind. For SUPPORT the list is hardcoded and contains a single item; for BUG and FEATURE an LLM generates a list shaped to the ticket's content.

KindCountHow generatedExample
SUPPORTexactly 1deterministic, no LLM call"Review & send reply" → Support Engineer
BUG3–6LLM, dev-focusedreproduce · root cause · regression test · fix · verify
FEATURE3–5LLM, triage-focusedvalidate demand · scope · prioritise · then build

For SUPPORT the work is simple: the draft reply lives in the Auto-reply panel and the action points you to it. For BUG and FEATURE the Coordinator pulls the issue's title, summary, impact and flags into a prompt to build a list that fits.

Action types and priorities

Each item has a type, a priority, a suggested owner role and a due window.

  • Types: support (re-contact the customer), commercial (sales/pricing/validation), operational (dev/build/deploy), configuration (env/settings)
  • Priorities: urgent · high · normal · low
  • Owner role: short label, e.g. "Developer", "QA", "Product", "CTO"
  • Due window: free text — "today", "within 24h", "this week"
  • Risky flag: items that touch payment, auth or user data are rendered with a red border

Statuses

Each item moves through four statuses:

  • open — not picked up yet (default)
  • in_progress — click Start to move it here
  • done — tick the checkbox
  • cancelled — use Remove to clear it

Updates are optimistic: the UI flips immediately, the server follows.

Generating and regenerating

For a fresh BUG or FEATURE issue you'll first see "No actions yet". Click Generate actions to have the Coordinator build the list. For SUPPORT the single item appears straight away.

Regenerating replaces every item with status open. Items you've already moved to in_progress, done or cancelled stay put — your work is not lost.

FAQ

Can I add an action item manually? Not from the UI. Items are produced by the Coordinator (and by automatic handoffs like QA→dev).

Why doesn't SUPPORT generate a list of four items? Because SUPPORT work is exactly one thing: review and send the draft reply. More items would just be noise.

Does regenerating cost tokens? For BUG and FEATURE, yes — it triggers an LLM call. For SUPPORT it's free; the single item is generated deterministically.

Anything unclear or wrong?Let us know →

FixControl is a trade name of FixControl B.V. i.o.