File a monday.com item from the session that found the bug
Paste one API token, pick a board, and a failed test or a broken screen becomes an item on that board — with the detail you wrote and the screenshot that was on your display.
One API token. No marketplace app to install, no admin approval.
Checkout — assertion failed on the payment step
Chrome 152 on Windows 11. Payment step returned 500; full repro in the linked session.
Open item →
- One API token
- no marketplace app, no admin approval step
- 3 calls per filing
- read the account slug, create the item, post the update
- AES-256-GCM at rest
- the token is encrypted, the key lives outside the database
- One-way
- nothing reads state back out of monday.com
What gets filed, and how
One filing creates one item, carries the evidence, and stores a link back to the session that produced it.
An item on the board you select
The adapter calls create_item on the board you chose when you connected, stored as the organisation default. The picker lists your active boards and stops there — it is boards, one level, never groups.
The title is the only column that carries
The adapter sets the item name and no column values at all — no status, no person, no date, no priority, no dropdown and no numbers. A board viewed as a table shows the title and empty columns, so put enough in the title to triage from.
The detail and the screenshot, carried across
A monday item has no description field, so your reproduction notes are posted as the item's first update, and the screenshot is attached to that update. If the image exceeds the ceiling or monday refuses it, the item is still created and the result tells you it did not attach.
monday answers failures with a 200
GraphQL returns a failed create as HTTP 200 with an errors array, so every call reads the response body — a status check alone would report a false success and store a link to nothing. The same check catches an expired or revoked token, which monday returns inside an error body rather than as a 401.
Set up once by an administrator
The connection lives under Organization, then Integrations, then Project management. An admin pastes the API token and picks the board once; a tester filing from a session never sees that screen again.
Connect, not migrate
Filing creates new items and stores only the link — the product it came from, what it was filed against, and the item's id and URL. Nothing imports your board, nothing polls monday.com, and closing or deleting the item there changes nothing here.
What the item gets, and what it leaves empty
A monday item is a name and a row of columns. The adapter sets the name and posts the body as an update. It sets no column values at all.
Set on the item
- board_id — the board you chose, the organisation default
- item_name — the title you typed
- create_update — the body, as the item's first update
- Attachment — the screenshot, on that first update
Left empty
- Status column — set nothing; use a board automation if triage needs one
- Person column — the item arrives with nobody on it
- Date and priority columns — no date, nothing ranked
- Dropdown and numbers columns — whatever your board defines, all empty
Never touched
- No group picker — an item without a group lands in the board's default group.
- No subitems or linked boards — one item per filing, no connected-boards column.
- No status read-back — filing is one-way; nothing polls for changes.
- Calls per filing: read the account slug, create the item, post the body as an update
- 3
- monday API version pinned by the adapter
- 2024-10
- Active boards listed for you to choose from
- 200
- The stored API token is encrypted at rest
- AES-256-GCM
The load-bearing check: monday answers a failed GraphQL request with HTTP 200 and an errors array, so every call reads the response body — a status check alone would report success on a failed create. The same check catches an expired or revoked token, which monday returns inside an error body rather than as a 401, and turns it into a plain instruction to reconnect. The token is encrypted before storage with a random 12-byte initialisation vector and an authentication tag, and no endpoint hands a stored credential back.
Frequently asked questions
Yes. A failed test or a broken screen becomes an item on the board you chose, with your reproduction notes and the screenshot posted as the item's first update. Filing is one-way — nothing reads state back out of monday.com.
One monday.com API token, and nothing else. There is no marketplace app to install, no OAuth consent screen and no admin approval step. You paste the token, TestKase lists your active boards, and the one you choose becomes the organisation default.
Because a monday item has no description field. The adapter creates the item with its name and immediately posts the body as the item's first update. One consequence is worth knowing: a board view that shows only columns will not show that text, so someone scanning the board sees the title and has to open the item to read the rest.
No. The adapter sets no column values at all — no status, no person, no date, no priority, no dropdown and no numbers. The item arrives in the board's default group with its name and its first update. If your triage depends on a status being set at creation, set it with an automation on your side; it will fire on the items we create.
No. The picker lists active boards and stops there — boards, one level, never groups. An item created without a group goes into the board's default group, and moving it afterwards is a drag on the board. A group picker is a reasonable thing to want; it is not built.
No. Filing is one-way. TestKase stores the item id and its URL against the session, scan or test that produced it, so you can always get from the evidence to the item, but nothing polls monday.com and nothing reads a status back. Closing, archiving or deleting the item has no effect here.
Yes. Defect trackers and project-management tools are separate connections, so an organisation can hold a bug tracker and monday.com at once, and the filing dialog asks which one you want. What you cannot do is connect two project-management tools at the same time: connecting Asana, Trello or ClickUp replaces monday.com.
Connect monday.com and file the next one from the session
Start free, paste a token, pick a board. See the rest of what TestKase connects to on the integrations overview.