Contact your administrator to integrate with Jira message on TestOps

I have been trying to figure out why the bug icon in TestOps constantly displays this message “Contact your administrator to integrate with Jira or ADO”.

Jira is connected from TestOps. I can select release versions and sprints just fine.
I have the Jira app installed in our Jira cloud instance too, and that’s also connected just fine and displays the related test cases without issue.

I am a Jira administrator and also the Project owner in Katalon, so I have all the access rights to both that I need. My Jira token is not set with any scope, so it should have all the same permissions and rights that I have when logged into Jira.

Does anyone know why this not functioning or is there a more up to date guide for integrating Jira that actually shows how what is required.

Hoping someone knows a simple solution to this one that I’m missing. Thanks in advance.

2 Likes

Problem Analysis

You’re experiencing an issue where the Report Defect feature (bug icon) in TestOps displays “Contact your administrator to integrate with Jira or ADO” even though:

  • Jira is connected at the account level
  • You can see releases and sprints
  • The Katalon plugin is installed in Jira
  • You have all necessary permissions

The issue is that Report Defect is a separate feature from basic Jira integration and requires specific configuration at the project level that goes beyond just connecting Jira.

Root Cause & Solution

Based on the official Katalon documentation, the Report Defect feature requires Bug Mapping to be explicitly enabled during the project-level Jira integration setup. Here’s what you need to do:

Step 1: Verify Project-Level Jira Configuration

  1. Navigate to your Project > Settings > Integrations
  2. Find your linked Jira integration and click the Settings (gear) icon
  3. Go to Step 2: Additional integration settings
  4. Ensure “Bug Mapping (Pull bugs from Jira)” is ENABLED :white_check_mark:

This is the critical step that enables the Report Defect functionality. If this checkbox is not ticked, the Report Defect feature will not work.

Step 2: Complete the Bug Mapping Configuration

If you enable Bug Mapping, you’ll need to complete the following additional steps:

  • Step 3: Configure Release and Sprint Mapping
  • Step 4: Map Common Fields (Priority levels)
  • Step 6: Map Bug Fields and Values (Severity, Status, Resolution)

Step 3: Verify Jira Permissions

According to the official documentation, the Report Defect feature requires these specific Jira permissions:

Feature Required Permission(s)
Create Defects Browse Projects, Create Issues
Optional (if fields are required in Jira) Assign Issues, Modify Reporter, Link Issues, Resolve Issues

Important: Even though you have a Jira token with no scope restrictions, verify that your token actually has these permissions by:

  1. Testing the connection in TestOps (click Test Connection)
  2. Checking if the token was generated with the correct scopes in Jira

Step 4: Finalize the Configuration

After enabling Bug Mapping and configuring all required fields:

  1. Click Proceed to sync data and finalize the connection
  2. Reload the page to ensure the status updates to Active

Key Considerations

  • Bug Mapping vs. Basic Integration: You can view releases and sprints with just basic Jira integration, but Report Defect specifically requires Bug Mapping to be enabled
  • Project-Level Configuration: This is different from the account-level Jira connection. Both are required
  • Webhook Setup: Service hooks are automatically created at the project level for real-time syncing
  • Field Requirements: If your Jira project has required fields beyond the standard ones, you may need additional permissions

References


Try this first: Go to your project’s Jira integration settings and verify that “Bug Mapping (Pull bugs from Jira)” is enabled in Step 2. This is most likely the missing piece. If it’s already enabled, try clicking Proceed again to re-sync the configuration, then reload the page.

The “Contact your administrator to integrate with Jira” message on TestOps bug icons appears when Bug Mapping is not enabled at the project level, even if account-level Jira connection works for releases/sprints.​

Project admins access Project Settings > Integrations, edit the Jira connection (gear icon), and in Step 2: Additional integration settings, toggle Bug Mapping (Pull bugs from Jira) on. Map Jira statuses/resolutions to TestOps equivalents, then click Proceed to sync—reload the page if status shows Inactive.​

Verification Steps

  • Confirm Katalon for Jira app is installed/enabled in your Jira Cloud project (Apps > Katalon Settings).​
  • Test by clicking the bug icon on a failed test result; it should now allow defect creation/linking without the admin message.​
  • Ensure your PAT token has full Jira scopes for bidirectional sync

hi @Sixstring

things to double-check:

  1. In TestOps → Project → Settings → Integrations → Jira

    • Make sure Defect Management / Report Defect is enabled, not just test management.
    • A lot of people miss that toggle.
  2. Check the issue type mapping

    • Bug issue type must be mapped explicitly.
    • If TestOps can’t find a valid Bug type, it shows that admin message.
  3. Jira permissions

    • The token user must be able to create issues in the target project.
    • Being a Jira admin isn’t enough if the project permission scheme blocks it.
  4. Jira Cloud + ADO note

    • That message is generic. Even if ADO isn’t used, it still appears when Jira defect config is incomplete.

Quick sanity check: try creating a defect from TestOps Defects tab, not from the execution screen. If that fails too, it’s definitely config, not UI.

Thanks. It’s resolved now.

There were two issues:

First was the active project I had Katalon connected to, did not have a bug issue type. This stopped me from using the bug configuration setting in the Katalon integration. Once I got that added, it worked.

The second issue was the connection in the Jira app had reset itself on some of the other projects and lost my api key to Katalon. As soon as I connected that side back to Katalon, the integrations all started to show active again, and let me report to any of the projects from TestOps.

Thanks to all the people who took the time to respond. I appreciate the help.

1 Like

Good that it is resolved

thanks @Sixstring for sharing the solution