What the Trello integration does

Every new comment on a project you route to Trello becomes a card on the board you choose, with the screenshot attached and the page and browser details in its description. On Trello, a card's list is its status, so status syncs both ways by moving cards: move a card to another list and its comment follows, change the comment's status in Huddlekit and the card moves. For an overview, see the Trello integration page.

Before you start

Plan: Trello is on the Team plan. See Understanding plans and pricing.
Role: only workspace owners and admins can connect Trello or change its settings. Other members can open Integrations and see that Trello is connected, but can't change anything.
Trello access: the Trello account you connect with needs edit access to every board you plan to use. A board you can only view can't take new cards.

Connect Trello

Open Integrations in your workspace sidebar.
Click Connect on the Trello row.
Approve Huddlekit on Atlassian's consent screen. Trello accounts sign in through Atlassian.
You land back on Integrations with the message Trello connected: "Nothing syncs until you choose a board for your projects."

Nothing is sent yet. Huddlekit doesn't guess a board for you, so the Trello row shows Not configured until you choose one.

Choose where each project's cards go

Open the ⋯ menu on the Trello row and choose Configure. The Trello settings dialog opens. Changes save as you make them, so Done just closes it.

Default board: where comments go from every project you don't set individually, including projects created later. Choose No default if only the projects you set should sync.
Projects: one row for each website, web app and media project. Leave a row on the default, pick a board of its own, or choose Don't sync to keep that project out of Trello even when a default is set.

Boards are grouped by Trello Workspace, and different projects can use boards from different Trello Workspaces. Huddlekit checks each board with Trello before saving it, so a closed board, a board you can only view, or a board with no lists won't save.

Changing a project's board only affects new comments. Cards that already exist stay where they are.

Map statuses to lists

Huddlekit has four statuses: Open, In review, In progress and Resolved. On a board, each list stands for a status, so every board has its own map. When you first choose a board, Huddlekit fills in its map from the board's lists:

Lists are matched by name, for example To Do or Backlog for Open, Review or QA for In review, Doing for In progress, and Done or Shipped for Resolved. The match has to be the whole name, so a list called "Done this week?" isn't matched.
If no list matches Open, it gets the leftmost list, as long as that list isn't named like Done or Won't do. No other status falls back to a list by position.
A list named like a cancellation is never picked for Resolved: names like Won't do, Blocked, On hold, Duplicate, Rejected, Archive, Out of scope, Not a bug, Deferred or Postponed. That way, parking a card doesn't tell a client their feedback is done.
Other lists named like Done also resolve the comment when a card moves to them, and other lists named like To Do set it back to Open.

To change the map, click the gear next to the Default board or any project row. Each Huddlekit status gets one list, or Never sync this status, which stops that status syncing in both directions. Several projects can share a board, and the dialog tells you when a change will apply to all of them. A board can have more lists than Huddlekit has statuses, so several lists can lead to the same status.

A status with nothing mapped shows a warning, and the row shows Status mapping incomplete. On a board with just To Do, Doing and Done, that's In review, so pick a list for it. A comment moved to a status with no list doesn't move its card, and a card moved to a list nobody mapped doesn't change its comment. A card moved to Blocked shouldn't tell a client their feedback is resolved.

Lists are tracked by their id, so renaming a list in Trello changes nothing. If you archive or delete a mapped list, that status shows as unmapped until you pick another.

What each card includes

Title: the comment number and the first line of the comment, like #42 — Logo is blurry on mobile. When several of your projects share a board, or the board is the default, the project name goes in front: [Acme site] #42 — ….
Description: the full comment, the project, who reported it, where it was left, and a link to open the screenshot. Where it was left is a link to the page on a website, and the page number or video time on a media file. Media comments have no screenshot.
Environment: OS, browser, resolution, viewport, pixel ratio, color depth and network, whichever were captured. Website comments carry the most. Web app comments carry fewer, and media comments have none.
Open in Huddlekit: a link back to the comment.
Screenshot: attached to the card as well, named Screenshot.

New cards go to the top of their list, so the newest feedback is the first card you see. Private comments are sent too, so think about who can see a board before routing a project to it. A new comment usually reaches Trello within about a minute.

What stays in Huddlekit

Status is the only thing that syncs, and the list a card sits in is the only thing read back from Trello. The card description is written once, when the comment arrives, so later edits to the comment text aren't pushed. Replies, priority, tags and assignees stay in Huddlekit. Labels, members, due dates, checklists and comments your team adds in Trello stay in Trello.

Comments aren't copied over later if they were left before you connected, before their project had a board, while it was set to Don't sync, or while syncing was paused. If one of them changes status later and its project syncs, it becomes a card then.

A few things happen to cards on the Trello side:

Archived cards: archiving a card doesn't change its comment. If the comment is reopened, the card comes back from the archive into the matching list.
Deleted cards: deleting a card doesn't delete the comment. Its status just stops syncing, and the card isn't created again.
Cards moved to another board: if the new board is also one of your Huddlekit boards, the card keeps syncing there. Otherwise its status stops syncing.

One-way sync

If you'd rather keep changes made in Trello from coming back, open the ⋯ menu and choose Switch to one-way sync. The option appears once a project or the default has a board. Changes made in Trello then stay in Trello, including during the nightly check. Comments still become cards, and changing a comment's status still moves its card. Switch to two-way sync in the same menu turns it back on.

Nightly check

Once a night, Huddlekit compares linked cards with their comments and fixes statuses that drifted, for example after a missed update. If only the card moved, the comment follows it, unless the connection is set to one-way sync. If the comment changed since it last synced, Huddlekit wins: the card is moved back, and a comment on the card explains why. The same check restarts two-way sync if Trello has stopped sending updates.

Disconnecting

Open the ⋯ menu and choose Disconnect. No more comments are sent, and cards already in Trello stay there. To finish, remove Huddlekit from the connected apps in your Atlassian account settings.

If you connect again later, your boards, status maps and card links come back, and existing cards keep syncing instead of being created twice.

If your plan changes

Syncing only runs while the workspace is on the Team plan with its payments up to date. If the workspace moves to another plan, or a payment is past due, the Trello row shows Paused and nothing syncs in either direction. Comments left during that time aren't queued up to send later. Your settings are kept, and Disconnect stays available.

Once the workspace is back on Team, the nightly check repairs cards that already exist, the same way it does any other night.

Troubleshooting

If connecting doesn't finish, you're returned to Integrations with a Trello not connected message and the reason:

"Could not read your Trello account. Try again." or "Trello did not grant lasting access. Try again." Click Connect again.
"Trello refused the access Huddlekit asked for. Contact support." Email support@huddlekit.com and we'll look into it.
"Cancelled. Nothing changed." You cancelled on Atlassian's screen. Click Connect again when you're ready.
"That link expired. Start again." Too much time passed on Atlassian's screen. Click Connect again.
"You switched accounts partway. Sign back in and retry." You were signed in to Huddlekit as someone else by the time you came back. Sign in as the admin who started, then connect again.
"That link was already used. Start again." or "That link was not valid. Start again." Click Connect again from Integrations.
"Only workspace admins can do this." or "Needs the Team plan." Ask an owner or admin, or upgrade the workspace first.
Anything ending in "Try again." Click Connect again.

Sync failing on the Trello row means a comment couldn't be sent to Trello and won't be retried, for example because its board was closed. Open Configure from the ⋯ menu and hover over Sync failing for the reason. It clears once a comment syncs to Trello again.

A board won't save. Huddlekit checks each board with Trello before saving it:

"That Trello board is closed. Pick another, or reopen it."
"Your Trello account can only view that board, so it cannot add cards. Pick another, or ask for edit access."
"That Trello board has no open lists. Add one, or pick another board."
"Trello could not find that board, or your account cannot reach it."
"Trello refused the connection. Reconnect Trello."

Two-way sync delayed or Two-way sync not set up means list changes made in Trello aren't coming back yet. New comments still become cards. Choose Resume two-way sync in the ⋯ menu. If you see "Trello did not accept the webhook. Try again, or Reconnect in the ⋯ menu.", try Reconnect. Your boards, status maps and card links are kept.

If Trello stops accepting Huddlekit, for example after a password change or a long time without use, choose Reconnect in the ⋯ menu. Nothing is lost.

Connecting Trello