Integrations

From test to ticket: effortless bug tracking with ReportPortal

arrow leftBack to blog
userReportPortal Team
calendarJuly 8, 2025

If you're looking to improve bug visibility and optimize test management workflows, integrating bug tracking systems (BTS) with ReportPortal is an efficient way. This allows you to log, view, and manage issues, making defect tracking smoother and faster.

This article explores the most popular BTS plugins supported by ReportPortal, their features, and how they can enhance your QA process.

What are BTS plugins?

BTS plugins connect ReportPortal to external issue tracking. This allows you to: 

  • Submit tickets right from failed test cases. 

  • Link issues to test results for better traceability. 

  • View existing issues without switching tools.

Benefits of integration with BTS

  • Easier bug reporting No need to open your BTS and create defects manually – create bugs right from ReportPortal in just a few clicks.

  • High-quality bug reports Bugs come with all the necessary logs and attachments automatically included – no extra effort required.

  • Real-time sync Track bug progress without leaving ReportPortal, thanks to automatic status synchronization with your BTS.

  • Link to existing bugs Easily connect test failures to existing issues using their IDs – no duplication, full traceability.

Supported BTS in ReportPortal

Let’s take a look at the BTS plugins available in ReportPortal.

1. Jira Server

Jira Server was replaced by Jira Data Center in 2021. ReportPortal supports integration with Jira Data Center as well.

Ideal for: Enterprises with private infrastructure and advanced Jira configurations.

Characteristics: 

  • Deployment type: On-premises (self-hosted) 

  • Free plan: Not available 

  • Issue type selection: Supported (e.g., Defect, Story, etc.) 

  • Custom field mapping: Supported 

  • Real-time synchronization: Supported 

  • Issue linking: Supported (e.g., blocks, duplicates) 

  • Test-to-issue linking: Supported 

  • Automatic context sharing: Logs, screenshots, and comments attached 

  • OAuth support: Not supported 

  • Automation capabilities: None 

  • Unique features: Self-hosted Jira with workflow integration 

Integration instructions

2. Jira Cloud

Ideal for: Agile teams using Atlassian Cloud for fast-moving product development.

Characteristics: 

  • Deployment type: SaaS (Cloud) 

  • Free plan: Available for a limited number of users 

  • Issue type selection: Supported (e.g., Bug, Task, etc.) 

  • Custom field mapping: Supported 

  • Real-time synchronization: Supported 

  • Issue linking: Supported (e.g., blocks, duplicates) 

  • Test-to-issue linking: Supported 

  • Automatic context sharing: Logs and attachments included 

  • OAuth support: OAuth 2.0 supported 

  • Automation capabilities: Limited, depends on Jira config 

  • Unique features: Cloud-native Jira integration with secure auth 

Integration instructions

3. Azure DevOps

Ideal for: Microsoft-centric teams managing projects through Azure DevOps.

Characteristics: 

  • Deployment type: SaaS 

  • Free plan: Available for a limited number of users 

  • Issue type selection: Supported (e.g., Task, Bug, etc.) 

  • Custom field mapping: Basic support 

  • Real-time synchronization: Supported 

  • Issue linking: Limited support 

  • Test-to-issue linking: Supported 

  • Automatic context sharing: Logs and test data shared 

  • OAuth support: Not supported 

  • Automation capabilities: Not available 

  • Unique features: Area/Iteration Path config; Microsoft ecosystem 

Integration instructions

4. GitLab

Ideal for: Teams using GitLab for both version control and issue tracking.

Characteristics: 

  • Deployment type: Cloud and Self-managed 

  • Free plan: Available for a limited number of users 

  • Issue type selection: Supported via CI/CD failures 

  • Custom field mapping: Labels and milestones 

  • Real-time synchronization: Supported 

  • Issue linking: Basic linking supported 

  • Test-to-issue linking: Supported 

  • Automatic context sharing: From failed tests 

  • OAuth support: Not supported 

  • Automation capabilities: Not available 

  • Unique features: Tight CI/CD integration, test results in pipelines 

Integration instructions

5. Monday

Ideal for: Product-focused teams using Monday for visual tasks and bug tracking.

Characteristics: 

  • Deployment type: SaaS 

  • Free plan: Available for a limited number of users 

  • Issue type selection: Via board items 

  • Custom field mapping: Maps test metadata to board columns 

  • Real-time synchronization: Two-way sync via automations 

  • Issue linking: Basic, through board structure 

  • Test-to-issue linking: Supported 

  • Automatic context sharing: Logs and test info included 

  • OAuth support: Supported 

  • Automation capabilities: Rich built-in automations 

  • Unique features: Visual boards and workflow triggers 

Integration instructions

6. Rally

Ideal for: Large organizations managing high-complexity Agile portfolios.

Characteristics: 

  • Deployment type: SaaS (Enterprise-grade) 

  • Free plan: Available for a limited number of users 

  • Issue type selection: Supported (with tagging, severity, etc.) 

  • Custom field mapping: Supported 

  • Real-time synchronization: Supported 

  • Issue linking: Full traceability 

  • Test-to-issue linking: Supported 

  • Automatic context sharing: With issue submissions 

  • OAuth support: Not supported 

  • Automation capabilities: Limited/custom 

  • Unique features: Hierarchical teams and Agile portfolio management 

Integration instructions

With our plugins, every failure is linked to the work item in BTS, along with logs, screenshots, and comments – so there’s no confusion and nothing gets lost. By having this data, teams eliminate the need to switch between tools, allowing them to detect, report, and resolve issues more quickly.