Trello Integration

Connect BugBrain to Trello to automatically create cards when tests fail, track testing progress, and keep your team organized with visual boards.

What Can You Do?

Automatic Card Creation

When tests fail, BugBrain can:

• Create Trello cards automatically
• Add test details, screenshots, and logs
• Set labels based on priority
• Assign to team members
• Place in specific lists

Visual Test Tracking

Keep testing organized:

• Track bugs on Trello boards
• Move cards through workflow stages
• See testing status at a glance
• Link cards to test executions

Team Collaboration

Work together effectively:

• Comment on cards from BugBrain
• Update card status
• Attach screenshots and logs
• @mention team members

Setting Up Trello Integration

Prerequisites

You need:

• Trello account (free or paid)
• Admin access to Trello board
• Admin or owner role in BugBrain
• Available on Growth and Pro plans

Step 1: Generate Trello API Key

1. Go to Trello Power-Ups Admin
2. Click “New” to create a new Power-Up
3. Enter name: “BugBrain Integration”
4. Generate API Key
5. Copy the API Key (save it!)

Step 2: Get Trello Token

1. While on the Power-Ups page, click “Token”
2. Or visit: https://trello.com/1/authorize?expiration=never&name=BugBrain&scope=read,write&response_type=token&key=YOUR_API_KEY
3. Replace YOUR_API_KEY with your key from Step 1
4. Click “Allow”
5. Copy the token (save it!)

Step 3: Connect to BugBrain

1. Go to BugBrain → Settings → Integrations
2. Click “Connect” next to Trello
3. Enter your credentials:
   • API Key: From Step 1
   • Token: From Step 2
4. Click “Connect”
5. BugBrain will verify and load your boards

Step 4: Select Board and List

Choose where to create cards:

1. Select Board: Pick the Trello board for test failures
2. Select List: Choose which list for new cards (e.g., “To Do”, “Bugs”, “Backlog”)
3. Default Labels: Add labels to all created cards
4. Click “Save”

Step 5: Configure Card Creation

Choose when to create cards:

Trigger Options:

• Every failure - Card for every failed test
• Recurring failures - Only after X consecutive failures
• New failures - Only for tests that previously passed
• Critical failures - Only for high-priority tests
• Manual only - Only when you click “Create Card”

Configure:

1. Settings → Integrations → Trello → Configure
2. Select trigger type
3. Set failure threshold (if using recurring)
4. Enable/disable per project
5. Save settings

Using the Integration

Automatic Card Creation

When a test fails and triggers are met:

1. BugBrain creates card in configured list
2. Card includes:
   • Title: Test name
   • Description: Failure details
   • Labels: Based on priority/tags
   • Attachments: Screenshots
   • Checklist: Test steps
   • Due Date: Optional
3. Card linked to test execution
4. Notification sent (if enabled)

Card example:

Title: [BugBrain] Login test failed

Description:
Test: User login with valid credentials
Project: Production App
Priority: High
Status: Failed
Duration: 15s

Error: Element not found: #login-button

Steps Performed:
1. Navigate to /login
2. Enter email: test@example.com
3. Enter password: ******
4. Click login button ← Failed here

View in BugBrain: [link]

Labels: bug, high-priority, bugbrain

Manual Card Creation

Create cards on demand:

1. Go to failed test execution
2. Click “Create Trello Card”
3. Review auto-filled details
4. Choose board and list
5. Add additional info if needed
6. Click “Create”

Use case: For selective card creation or when you want to add context before creating.

Viewing Linked Cards

See Trello cards linked to tests:

In Test Execution:

• “Linked Cards” section shows related Trello cards
• Click to open in Trello
• See card status

In Test Case:

• View all cards created from this test
• Track which are resolved
• See failure history

Card Templates

Customize card content:

Title Template

Default: [BugBrain] {{testName}} failed

Variables:

• {{testName}} - Test case name
• {{project}} - Project name
• {{priority}} - Test priority
• {{status}} - Pass/Fail/Warning

Example: 🐛 {{testName}} - {{priority}}

Description Template

Customize card description:

**Test:** {{testName}}
**Project:** {{project}}
**Priority:** {{priority}}
**Status:** {{status}}
 
## Failure Details
{{errorMessage}}
 
## Steps to Reproduce
{{testSteps}}
 
## Environment
{{environment}}
 
## Additional Info
- Execution ID: {{executionId}}
- Failed at: {{failedAt}}
- [View in BugBrain]({{executionUrl}})

Configure templates:

1. Settings → Integrations → Trello → Card Template
2. Edit title and description
3. Use variables for dynamic content
4. Preview
5. Save

Labels and Organization

Automatic Labels

BugBrain can automatically add labels:

Priority-based:

• Critical → Red label “critical”
• High → Orange label “high”
• Medium → Yellow label “medium”
• Low → Green label “low”

Type-based:

• All cards → “bugbrain” label
• Test failures → “test-failure” label
• Discovery issues → “discovery” label

Configure:

1. Settings → Integrations → Trello → Labels
2. Map BugBrain properties to Trello labels
3. Create labels in Trello if needed
4. Save mappings

Custom Labels by Tag

Map test tags to Trello labels:

Example mappings:

• Test tagged “smoke” → Trello label “smoke-test”
• Test tagged “regression” → Trello label “regression”
• Test tagged “api” → Trello label “api-test”

Label Colors

Organize visually with colors:

• 🔴 Red - Critical bugs
• 🟠 Orange - High priority
• 🟡 Yellow - Medium priority
• 🟢 Green - Low priority
• 🔵 Blue - Needs investigation
• 🟣 Purple - Test automation

Advanced Features

Card Checklists

Add checklists to cards automatically:

Default checklist:

• ☐ Reproduce the issue
• ☐ Identify root cause
• ☐ Implement fix
• ☐ Verify test passes
• ☐ Deploy to production

Custom checklists:

1. Settings → Integrations → Trello → Checklists
2. Create checklist templates
3. Assign to card types
4. Save

Automatic Assignments

Auto-assign cards to team members:

Assignment rules:

• Test owner → Card assigned to them
• Project owner → Card assigned to project lead
• Round-robin → Distribute among team
• By tag → Tests tagged “backend” → backend team

Configure:

1. Settings → Integrations → Trello → Assignments
2. Map BugBrain users to Trello members
3. Set assignment rules
4. Save

Due Dates

Set due dates automatically:

Options:

• Critical tests → Due in 1 day
• High priority → Due in 3 days
• Medium → Due in 1 week
• Low → Due in 2 weeks

Configure:

1. Settings → Integrations → Trello → Due Dates
2. Set rules by priority
3. Choose business days or calendar days
4. Save

Card Updates

Keep cards in sync:

Auto-updates:

• Test passes → Add comment to card
• Test fails again → Update card description
• Screenshot available → Attach to card
• Execution rerun → Add comment with results

Trigger rules:

1. Settings → Integrations → Trello → Updates
2. Choose events that update cards
3. Configure update behavior
4. Save

Multiple Boards Setup

Why Use Multiple Boards?

Different types of work need different boards:

• Bug Board - Test failures and bugs
• QA Board - Testing progress and tasks
• Sprint Board - Current sprint work including testing
• Backlog Board - Future test improvements

Setting Up Multiple Board Connections

1. Create separate connections for each board
2. Configure triggers for each:
   • Bug Board: All test failures
   • QA Board: Discovery results and test plans
   • Sprint Board: Critical failures only
3. Name connections clearly

Project-Specific Settings

Override global settings per project:

1. Go to Project Settings → Integrations
2. Click Trello
3. Override:
   • Different board/list
   • Different labels
   • Custom templates
   • Different triggers
4. Save

Use case: Different projects use different Trello boards.

Commenting and Updates

Add Comments from BugBrain

Add context to Trello cards:

1. Open failed execution with linked card
2. Click “Add Comment to Trello”
3. Type comment (markdown supported)
4. Click “Post”
5. Comment appears in Trello

Two-Way Sync (Pro)

Keep comments and status in sync:

From Trello to BugBrain:

• Comments in Trello → Show in BugBrain
• Card archived → Test case marked reviewed
• Card moved to “Done” → Failure marked resolved

Configure:

1. Enable webhook in Trello
2. Settings → Integrations → Trello → Sync
3. Enable two-way sync
4. Save

Bulk Operations

Create Multiple Cards

Create cards for multiple failures:

1. Go to Test Executions
2. Filter by failed status
3. Select multiple executions
4. Click “Create Trello Cards”
5. Review and create in bulk

Move Cards in Bulk

Update multiple cards at once:

1. Go to Test Cases
2. Select tests with linked cards
3. Click “Update Trello Cards”
4. Choose action (move list, add label, etc.)
5. Apply to all selected

Best Practices

Troubleshooting

Connection Issues

“Invalid API key” error:

• Verify API key is correct
• Ensure no extra spaces
• Try regenerating in Trello
• Check token hasn’t expired

“Board not found” error:

• Verify you have access to the board
• Check board wasn’t deleted
• Ensure token has read/write permissions
• Try reconnecting integration

Card Creation Fails

“Cannot create card” error:

• Check list still exists in board
• Verify permissions on board
• Ensure labels exist (or disable auto-labeling)
• Review error logs in Settings

Cards not appearing:

• Verify triggers are met
• Check filter settings
• Ensure integration is enabled
• Look in correct board/list

Permission Issues

“Permission denied” error:

• Token needs read/write scope
• Verify you’re admin on board
• Check workspace permissions
• Try regenerating token with full permissions

Security & Privacy

Data shared with Trello:

• Test names and descriptions
• Failure details and error messages
• Screenshots (if enabled)
• User names
• Project names

Data NOT shared:

• Passwords or credentials
• API keys or secrets
• Billing information
• Unrelated test data

API credentials:

• Stored encrypted in BugBrain
• Never logged or exposed
• Can be revoked in Trello anytime
• Recommend rotating periodically

Rate Limits

Trello API limits:

• 300 requests per 10 seconds per token
• 100 requests per 10 seconds per user
• BugBrain respects limits and throttles automatically

Recommendations:

• Use filters to reduce card volume
• Enable deduplication
• Batch operations when possible

Quota & Limits

Integration limits by plan:

Next Steps

• Set up Jira integration for enterprise issue tracking
• Configure Slack notifications for real-time updates
• Use webhooks for custom workflows
• Learn about team management