Tuskr X Jira Integration

Bidirectional Workflow for managing bug tracking

Client Challenge: 

Our client's QA and development teams were struggling with disconnected systems. 

When tests failed in Tuskr, testers had to manually create Jira tickets with all the relevant information. When developers fixed issues in Jira, testers had to manually update test statuses in Tuskr. 

This disjointed process led to inconsistent documentation, delayed bug fixes, and a lack of visibility across teams.

Our Solution: 

We built a powerful bidirectional integration between Tuskr and Jira using Make.com that creates a seamless feedback loop between testing and development teams. 

Failed tests automatically create detailed Jira tickets, and when those tickets are updated, the corresponding test cases in Tuskr are automatically updated as well.

 Figure 1: Overview of the bidirectional integration workflow

What This Solved:

• Eliminated manual ticket creation and status updates

• Created perfect traceability between test cases and bug reports

• Ensured QA and development teams always have synchronized information

• Accelerated the bug fix verification process

• Provided comprehensive metrics on test failures and fixes

Customizations

Scenario 1: Tuskr → Jira (Test Failure Reporting)

When a test fails in Tuskr, the system automatically:

• Captures all test details including case name, run information, and tester comments

• Processes and formats the data for optimal readability in Jira

• Creates a standardized Jira ticket with rich formatting and clear context

• Embeds hidden tracking IDs to maintain bidirectional reference

 Figure 2: Tuskr to Jira workflow showing data capture and transformation

Scenario 2: Jira → Tuskr (Issue Resolution Tracking)

When a Jira ticket is updated or resolved, the system automatically:

• Detects changes through Jira webhooks

• Extracts the embedded test case and test run IDs from the issue description

• Sends an update to Tuskr with the new status (e.g., "RETEST")

• Includes relevant comments from the Jira issue

 Figure 3: Jira to Tuskr workflow showing issue tracking and status updates

Scenario 3: Rich Data Transformation

Our integration handles complex data with sophisticated processing:

• Cleans and standardizes text with regex pattern matching

• Creates beautifully formatted Jira tickets with tables and panels

• Preserves all context including hyperlinks back to original sources

• Handles special characters and multiline content correctly

 Figure 4: Example of rich data formatting in the created Jira issues

Technical Implementation Details

Tuskr → Jira Flow:

• Webhook captures test failure events

• JSON transformation prepares data for Jira's API

• Creates structured issues with Atlassian Document Format (ADF)

• Embeds hidden reference IDs for bidirectional tracking

• Returns success confirmation to Tuskr

Jira → Tuskr Flow:

• Watches for Jira issue updates via webhook

• Uses regex pattern matching to extract embedded test IDs

• Transforms Jira issue data to Tuskr's expected format

• Updates test status via Tuskr's REST API

• Preserves the complete context of the resolution

 Figure 5: Technical details of the Make.com workflows showing both integration directions

This bidirectional integration creates a perfect sync between testing and development teams. When tests fail, developers get immediate, detailed tickets. When issues are fixed, testers are automatically notified to verify the fixes. The entire process happens seamlessly without manual intervention, ensuring everyone has the same information and dramatically reducing the time from test failure to verified fix.