fenbs_create_item
Create a task on a fenbs board for features, enhancements, or bugs, with duplicate checks against open and recently finished tasks and an optional idempotency key for automated sources.
Instructions
Add a task to a board. Requires permission to add tasks. fenbs first checks the open tasks and the ones finished in the last 14 days: if one looks like the same thing, nothing is made and you get the likely matches (created: false). An open match: comment on it (fenbs_comment). A finished one ("finished" says how and when): move it back to To Do (fenbs_update_item lane "backlog") if it is the same thing back again, or call again with unlessSimilar: false and relatesTo its ref for a new task linked to it. Call again with unlessSimilar: false alone if yours is genuinely different. From an automated source, pass key: the same key never files twice. note is the problem (what, why, where); plan is how it will be done, when that is known -- keep the two apart. A free board near its limit adds a top-level plan notice (the free plan of the board: tasks left, and upgradeUrl; the plan of the task itself is inside created): tell your user how many are left and give them the upgradeUrl. A refusal with upgradeUrl (a full or read-only board) is the same: relay the message and give them the link.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | Optional, for automated sources (a Sentry issue id, a CI job, an error fingerprint): a live task with this key is returned instead of a new one. Up to 120 characters. | |
| kind | Yes | ||
| lane | No | The lane, by its key. People see backlog as To Do, next as Next Up, doing as In Progress and done as Completed: use those names when you talk to people. | |
| note | No | The Problem box: what is wrong or missing, why it matters, and where -- file and line for code; repro steps for a bug. Written once; the fix goes in plan, not here. | |
| plan | No | The Plan box: how it will be done -- the steps, the files to change, the traps, and how it will be checked. Leave it out until somebody knows; do not put a PLAN heading in the note instead. | |
| size | No | How big: xs (under an hour), s (an afternoon), m (a day or two), l (about a week), xl (too big -- split it). "none" takes a size off. | |
| board | Yes | ||
| title | Yes | ||
| project | No | The project this belongs to, by name -- for software, usually the repository or app. A new name creates the project; case is ignored when matching, so reuse the names fenbs_list_boards shows. | |
| category | No | An optional second grouping, by name, e.g. "Checkout" or "Mobile". A new name creates it. | |
| priority | No | 1 is most urgent. 1-2 High, 3-5 Medium, 6-10 Low. Leave it out for 5, an ordinary task. | |
| relatesTo | No | Refs of tasks this one relates to -- e.g. the finished task a bug has come back from. Linked both ways. | |
| testNotes | No | How it was tested: what was checked, where (dev, a private API, live), the result -- and what was NOT checked. Rewritten whole, like plan; "" clears it. | |
| testStatus | No | How it was tested: untested (the default), tested, partly, failed, or needs-check -- what only a person can confirm (a store build, a real payment, a live page). Never claim tested for a check you did not run; use needs-check or partly and say what is left. | |
| unlessSimilar | No | Default true: hold back when an open or recently finished task looks like the same thing. false files it regardless. |