What action items are
Action items are the concrete follow-up steps for an issue. They appear in the Action items panel on the issue detail page, where you tick them off, start them, or remove them. Most are produced by the Workflow Agent; the panel's byline still calls it Operations Coordinator, which is the same agent.
Who can use them
Anyone who can read an issue sees its action items. Generating, ticking off, starting and removing items needs the admin or manager role.
What you get per kind of issue
| Kind | What appears | How it is made |
|---|---|---|
| SUPPORT | Exactly one item: "Review & send reply" for the Support Engineer. | Fixed rule, no AI call. |
| FEATURE | 3–5 items in the order you'd do them: validate demand, scope the smallest first cut, prioritise against the roadmap, and only then build. | The Workflow Agent reads the issue's title, summary, impact, flags, body and any attached screenshots. |
| BUG | No generated items. | The AI mission does the investigation, fix and verification itself, so a generated to-do list would only repeat finished work. |
For SUPPORT and FEATURE issues the list is generated automatically when the issue is created. The text follows the language of the issue: a Dutch issue gets Dutch items.
On a BUG issue the panel only appears when a QA handoff has written items into it: test work that QA passed back to development after verification. The byline then reads QA handoff, and there is no Generate actions button.
What each item shows
- Title — what to do.
- Priority —
urgent,high,normalorlow. - Type —
support(get back to the customer),commercial(demand, pricing, validation),operational(design, build, deploy) orconfiguration(setup, environment). - Owner role — who should do it, for example Developer, QA, Product, CTO or Support Engineer.
- Due window — free text such as "today" or "within 24 hours".
- Reason — why the step is there.
- risky — items that touch payments, authentication or an existing integration get a red border and a risky label.
Working with items
- Tick the box to mark an item done. Tick it again to reopen it.
- Start sends the item to the agent for its owner role (Developer, QA, Codebase Analyst, CTO or Support Engineer). A result line appears under the item. The item moves to in progress only when the agent run actually started; if the run fell back, was limited or failed, the item stays open so you can start it again. Roles without an agent (Product, for example) answer with manual task: that step is for a person.
- Remove deletes the item after you confirm. The mission timeline and audit history keep the record that it existed.
Generating and regenerating
If a SUPPORT or FEATURE issue has no items yet, the panel says No actions yet and offers Generate actions. Once there are items, the button reads Regenerate.
Regenerating replaces the whole generated list. Every item the Workflow Agent made is deleted, whatever its status (open, in progress or done), and a fresh list is written. Only QA handoff items survive. If you want to keep a record of what was done, tick items off and leave the list as it is rather than regenerating.
When it does not work
| What you see | What it means |
|---|---|
| No Action items panel on a BUG issue | Expected: BUG issues get no generated items. The panel appears once a QA handoff adds items. |
| No actions yet on a new FEATURE issue | The automatic generation did not finish. Click Generate actions. |
| An error under the header after generating | The AI call failed. Try again in a moment. |
| manual task after Start | No agent exists for that owner role. Do the step yourself and tick it off. |
FAQ
Can I add an action item manually? Not from the UI. Items come from the Workflow Agent and from QA handoffs.
Why does SUPPORT get only one item? Because SUPPORT work is one thing: review and send the draft reply in the Auto-reply panel. More items would just be noise.
Does generating cost AI usage? For FEATURE issues, yes: it makes an AI call. For SUPPORT it does not; the single item comes from a fixed rule. For BUG nothing is generated.
Related
- Issues — the issue detail page and the AI mission.
- Auto-reply — where the SUPPORT reply is drafted and sent.