Send the bug to the column your team actually watches

Trello's API authenticates with a key and a token together: the key identifies the application, the token identifies you and what you have allowed it to do. They are generated in different places and easy to mix up, the single most common setup mistake, so a wrong one comes back naming both rather than saying authentication failed. Both travel in the query string of every request rather than an authorisation header, which means an unhandled error object from a Trello call would carry the key and the token inside the request URL it reports on itself. Every call this adapter makes is therefore converted into a plain, message-only error before it can travel anywhere — a deliberate rule for this adapter specifically. Both values are encrypted at rest with AES-256-GCM and never returned by any endpoint. Trello attributes the card to the account whose token you connected, so use a service account if that attribution matters to you.

The one you chose when you connected. A Trello card has to live in a list, so the destination picker has two levels: it shows your open boards first, then the open lists on the board you pick. That list is stored as the organisation default and every filing uses it — there is no routing by product, platform or severity. Trello returns the new card's short URL, which is what we store and show, so the tester can open the card and whoever triages can follow the link back to the run.

The card is created with a list, a name and a description, and nothing else: no labels, no members, no due date, no checklist, no cover, no custom fields and no control over where in the column it appears. A Trello automation on the receiving list can add those after the card arrives, which is the better place for that rule to live anyway.

Yes, as a card attachment. The image travels with the filing request, is uploaded to the new card and is then discarded on our side — it is never written to our object storage. The card is created first and the image attached second, so if it exceeds the attachment ceiling or Trello refuses it, you still get the card and a note that the screenshot did not attach.

Trello answers with a bare 'invalid id', which is turned into a plain message telling you the list no longer exists and to choose another destination on the Project management page. A 401, or the bare bodies 'invalid key' or 'invalid app token', become an instruction to reconnect that names both the key and the Token so you know there are two values to check. Anything else is passed through in Trello's own words, and a status line, host name or stack trace never reaches the screen.

Filing is one-way — nothing watches the board and nothing reads a status back; what we keep is the link between the session or scan, the card id and the short URL Trello returns. An organisation holds one project-management connection and one defect-tracker connection, and both can be active together; the filing dialog asks which one you want. Connecting a second project-management tool replaces Trello rather than sitting alongside it.