File a bug from your assistant
When you finish, a new bug is on your board with the right type, priority and person. You type one sentence. It takes about a minute.
This works in any assistant connected to devBoard over MCP. MCP is the open standard that lets an AI assistant use other tools. Your words become a call to the create_item tool.
What you need
- An assistant connected to devBoard. See the Claude Code guide or the Cursor guide.
- Your role is member, admin or owner. A guest cannot create tasks.
- The project key, like APP, if the workspace has more than one project.
Steps
1. Say what is wrong
Start with "File a bug" and say what happens and where, in one sentence. For example: "File a bug in APP: the login button does nothing on iPad."
2. Say how bad it is
Add a priority word. devBoard has five: none, low, normal, high and urgent.
3. Say who should fix it
Add "assign it to me", a name, or an email. The name must match a member of the workspace. If two people share a name, use the email.
4. Send it
The whole request now reads: "File a bug in APP: the login button does nothing on iPad. Urgent, assign it to me." The assistant answers with the new key, like APP-57, and a branch name.
5. Add the details
Say: "Add steps to APP-57: open the app on iPad, tap Log in, nothing happens." The assistant puts them in the description.
How to ask so it gets it right
| You want | Say | What it sets |
|---|---|---|
| A bug, not a feature | "File a bug" | type: Bug |
| The right project | "in APP" | project |
| How urgent | "urgent", "high", "normal", "low" | priority |
| Who fixes it | "assign it to me", "assign it to Mira" | assignees |
| When it is due | "due tomorrow", "due 2026-10-16" | due date |
| A tag | "tag it ios" | tags (labels) |
| Under a bigger task | "under APP-40" | parent |
| In a release | "for release 1.4" | release |
Names must already exist. Types, tags and releases come from your workspace. If one is wrong, the assistant gets a list of the names that do exist and can try again.
New workspaces start with six types: Feature, Bug, Chore, Spike, Docs and Design.
Dates work best as "today", "tomorrow" or a full date like 2026-10-16.
An example: Ana
Ana is a freelancer with three clients. On Friday she tests the bakery app and finds that a coupon is taken off twice. She types: "File a bug in BAK: the coupon is applied twice at checkout. High, assign it to me, due tomorrow." The assistant files BAK-31 and gives her the branch name.
Check that it works
The new card is in the project's default column, usually To do. Open it and check the type, priority and assignee.
What to try next
- "Start APP-57." The assistant assigns you, moves the card to In progress and starts your timer. See start and finish work.
- "Break the onboarding epic into five tasks." An epic is a big piece of work split into smaller tasks.
- Track time on the fix with the timer on the task.
All how-tos are in the guides.
If it does not work
| What you see | Why | What to do |
|---|---|---|
| It has the wrong type | You did not say "bug" | Say "change APP-57 to a bug" |
| "No item type … Types: …" | An admin renamed the types | Use a name from the list |
| "No project … Projects: …" | The key is wrong | Use a key from the list |
| "No label … Labels: …" | Tags belong to a project and must exist | Pick one from the list, or ask an admin to add it |
| "No member … Members: …" | The name does not match anyone | Use their email |
| "Requires member or higher" | Your role is guest | Ask an admin to make you a member |
Questions people ask
Can my assistant add a tag that does not exist yet?
Only if you are an admin. Tags belong to a project, and only an admin can add one. A member can use the tags that are there.
Can it add a screenshot?
No. The MCP server cannot add attachments. Drop the file on the card in the app.
Free while in early access; paid plans will be one plain number, posted here first.
Download on the App Store Get it on Google Play Connect your AI assistant