QA TOUCH + TRELLO
Post QA Touch issues to the Trello list your team works from
Map Trello boards to your QA Touch projects, then post issues from test results into the list you choose and link tickets that already exist, without leaving QA Touch.
QA Touch finds the bug. Trello holds the card.
Connect your Trello account to QA Touch once, map Trello boards to your projects, and your test results can feed the boards, lists and cards where the team already organizes its work.
-
Problem: A bug found in a test run has to be re-entered as a Trello card.
With the integration: Select a list and post the issue; the card is created in that Trello list automatically.
-
Problem: Different projects keep their work on different Trello boards.
With the integration: QA Touch supports multiple Trello boards, mapped to projects at the project level.
-
Problem: Tickets that already exist in Trello stay disconnected from test results.
With the integration: Fetch Trello Tickets pulls tickets from the mapped boards so you can link them to results.
Sanity Testing Result
Illustrative sample data. “Sanity Testing Result” is the example list used in QA Touch’s Trello guide.
What the integration does
Five capabilities from QA Touch’s Trello guide and multi-board article, from the first connection to browsing your boards.
Connect with an API key and token
Create a Power-Up in Trello, generate its API key and token, then enter them under Administration → Integration Settings → Trello Settings. The status shows connected.
Map Trello boards to projects
QA Touch can integrate with multiple Trello boards. Mapping happens per project, and the boards from your Trello account appear in the list to choose from.
Post issues to a list
Use the Add Issue icon on the Test Run & Result page, select a list, fill in the details and save. The card is created in that list.
Link existing tickets
In the Add Result popup, Fetch Trello Tickets pulls tickets from all mapped boards so you can link them to test results.
Browse boards inside QA Touch
Integration Issues → Trello lists your connected boards. Open a board for its card lists, then a card for its items, and add, edit or view boards there.
From Trello Power-Up to card in a list
Step through the flow. The screens are schematic, drawn from the labels in the setup guide, not screenshots.
One-time Trello Power-Up API key and token
Get an API key and token from a Trello Power-Up
In the Trello Power-Up Admin Portal, create a Power-Up, generate its API key, then follow the Token link and click Allow to get your token.
Copy the token now. It cannot be viewed again after you leave the page.
QA Touch Administrator Administration → Integration Settings
Connect Trello in QA Touch
An Administrator opens Trello Settings, enters the API Key and API Token and clicks Update. The status shows connected.
QA Touch Projects → Project Mapping
Map Trello boards to a project
Open the project, go to Project Mapping, select a Trello board and click Submit. The boards in your Trello account appear in the list.
QA Touch Test Run & Result page
Post an issue to a list
Click the Add Issue icon on a result, select a Trello list, fill in the issue details and click Save.
Add Issue
QA Touch Trello board
The card appears in the list
The issue is created in the selected Trello list automatically, ready for the team to organize on the board.
Backlog
Sanity Testing Result
Done
Illustrative sample data. Board and list names are examples, except "Sanity Testing Result" from the guide.
What changes for your QA team
Testing stays in QA Touch. What it finds goes straight to where the work is planned.
No re-typing between tools
Testers post the issue from the result itself instead of switching to Trello to create a card by hand.
Issues land in your own structure
Cards arrive in the list you pick, on the board you mapped, so findings fit the way the team already organizes work.
Testing and development on one page
The people testing in QA Touch and the people working cards in Trello see the same issues instead of relaying them.
Connect once, reuse everywhere
An Administrator configures Trello globally one time. After that, each project only needs its boards mapped.
Who uses it, and for what
Choose a role to see a scenario the integration supports.
A team starts using Trello for its bugs
The team keeps its work on Trello boards and wants QA Touch connected to them before testing begins.
What they do
- Create a Power-Up in Trello and generate its API key and token.
- Enter both under Administration → Integration Settings → Trello Settings.
- Map the team's Trello boards to the project in Project Mapping.
Result: the project is connected, and testers can post to its boards.
A checkout test fails during a run
You are working through a test run and one result needs a Trello card for the team.
What they do
- Click the Add Issue icon on the Test Run & Result page.
- Select the Trello list that should receive it.
- Fill in the issue details and click Save.
Result: the card is created in that list automatically.
The bug is already on a Trello card
A teammate raised the problem in Trello before the test failed, and you want the result tied to that ticket.
What they do
- Open the Add Result popup.
- Click Fetch Trello Tickets to pull tickets from the mapped boards.
- Link the existing ticket to the test result.
Result: the result points at the Trello ticket, and no duplicate card is needed.
You work the cards in your Trello list
Findings from testing show up in the list where you already pick up work.
What they do
- Open the list the QA team posts to, for example Sanity Testing Result.
- Pick up the new card created from the test result.
- Move it through your board as you usually do.
Result: QA findings arrive as cards without anyone copying them over.
Set it up in three places
These steps follow QA Touch’s Trello integration guide: first in Trello, then in QA Touch, then per project.
Before you start
- A Trello account, logged in in your web browser.
- Access to the Trello Power-Up Admin Portal (opens in a new tab).
- A QA Touch Administrator login for the global configuration.
- Open the Trello Power-Up Admin Portal and click New.
- Enter a name for the Power-Up, select the associated Workspace, fill in the required contact information and click Create.
- In the Power-Up's settings, open the API Key tab and click the option to generate a new API key.
- Copy the key and store it securely.
- On the same page, click the Token link at the end of the explanatory paragraph, then click Allow.
- Copy the token right away. It cannot be viewed again after you leave the page.
The API key identifies your application. The token grants access to your Trello data, so keep it secret.
- Log in to QA Touch as an Administrator.
- Go to Administration → Integration Settings → Trello Settings.
- Enter the API Key and API Token.
- Click Update.
connectedThe status shows connected after a successful update.
- Click the project name in the projects list.
- Go to Projects → Project Mapping.
- Select a Trello board and click Submit.
- To post an issue, select a Trello list on the issue, fill in the details and click Save. The card is created in that list.
Boards mapped? See how an issue reaches a list.
Questions about the Trello integration
Answers are based on QA Touch’s integration guide, product page and blog posts.
What does the QA Touch Trello integration do?
It connects QA Touch to Trello so you can map Trello boards to projects and post issues from test results into a Trello list. It can also fetch Trello tickets from the mapped boards so you can link them to results.
What do I need before I set it up?
A Trello account logged in in your browser, access to the Trello Power-Up Admin Portal, and a QA Touch Administrator login for the global configuration.
Where do I get the API key and token?
Create a Power-Up in the Trello Power-Up Admin Portal. On its API Key tab, generate a new API key, then click the Token link and Allow to get the token. Enter both in QA Touch under Administration → Integration Settings → Trello Settings.
How should I handle the token?
Treat it as a secret. The guide explains that the API key identifies your application, while the token, combined with the key, can read from and write to your Trello account based on the permissions granted. It is shown only once, so copy it before leaving the page.
How do I post an issue to a Trello list?
Map a Trello board to the project in Project Mapping first. Then use the Add Issue icon on the Test Run & Result page, select a list, fill in the issue details and click Save. The card is created in the selected list.
Can I use more than one Trello board?
Yes. QA Touch supports integration with multiple Trello boards, and mapping is done at the project level. Integration Issues → Trello lists the connected boards, and Fetch Trello Tickets pulls tickets from all mapped boards.
Does anything sync back from Trello after a card is created?
The documentation describes posting issues to Trello and fetching Trello tickets to link them to results. It does not describe other syncing after a card is created, such as automatic updates when a card moves.
Connect Trello to QA Touch
Generate your Power-Up key and token, map a board to your first project, and post your next issue straight to a Trello list.