# Purpose of saving the Katalon Testcases from JIRA to Katalon TestOps

**URL:** <https://forum.katalon.com/t/purpose-of-saving-the-katalon-testcases-from-jira-to-katalon-testops/175731>\
**Category:** Integrations\
**Tags:** katalon-testops, testcasegenerator, integrations, web-testing, jira, katalon-studio\
**Created:** [June 9, 2025, 11:13am UTC](https://forum.katalon.com/t/purpose-of-saving-the-katalon-testcases-from-jira-to-katalon-testops/175731 "2025-06-09T11:13:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vasanthi.j](https://avatars.discourse-cdn.com/v4/letter/v/858c86/32.png) [@vasanthi.j](https://forum.katalon.com/u/vasanthi.j)\
**Post date:** [June 9, 2025, 11:13am UTC](https://forum.katalon.com/t/purpose-of-saving-the-katalon-testcases-from-jira-to-katalon-testops/175731/1 "2025-06-09T11:13:22Z")

</div>

Generated Testcases for userstory in JIRA using ‘Katalon-Testcase generator’ plugin

Integrated JIRA and Testops

Enabled ‘Save to katalon’ button and moved testcases to Testops

Query:

The testcases moved have referral JIRA ID.

1. What is the use of moving this testcases from JIRA to Testops
2. Is it possible to move this testcases to Katalon Studio and add testscripts
3. I manually added the same summary of the testcase in katalon studio and run and uploaded the report to Testops. But it got moved to Uploaded Data folder whereas the JIRA Testcases are moved to Katalon cloud folder. Is it possible to map this testcase
4. Need more details on this JIRA Integration uses in katalon

---

<div class="post-metadata">

**Author:** ![dineshh](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/dineshh/32/24488_2.png) [@dineshh](https://forum.katalon.com/u/dineshh)\
**Post date:** [June 10, 2025, 5:16am UTC](https://forum.katalon.com/t/purpose-of-saving-the-katalon-testcases-from-jira-to-katalon-testops/175731/2 "2025-06-10T05:16:26Z")

</div>

**Purpose of Moving Test Cases from JIRA to Katalon TestOps**

1. **Traceability & Visibility** :

- Link user stories (JIRA issues) directly to test cases in TestOps, ensuring **end-to-end traceability** (requirement → test case → execution result).
- Teams can track which tests validate specific JIRA user stories/epics.

1. **Centralized Test Management** :

- TestOps acts as a single source of truth for test cases, executions, and reports. Moving JIRA-generated test cases to TestOps ensures they are managed alongside automated/exploratory tests.

1. **Automation Synchronization** :

- Test cases in TestOps can be linked to automated scripts in Katalon Studio, bridging manual and automated testing workflows.

* * *

## **Moving Test Cases to Katalon Studio & Adding Scripts**

## **Option 1: Export Test Cases from TestOps to Studio**

- Use TestOps’ **“Link to Automation”** feature:
  1. In TestOps, open the test case imported from JIRA.
  2. Click **“Link to Automation”** and generate a placeholder script in Katalon Studio.
  3. Write automation code in Studio and map it to the TestOps test case via its **UUID** or **external ID**.

## **Option 2: Manual Script Creation with JIRA Mapping**

- If you manually create test cases in Studio:
  1. Add the JIRA issue key (e.g., `JIRA-123`) to the test case’s **description** or **custom fields** in Studio.
  2. Upload execution results to TestOps. Use **TestOps tags** or **JIRA IDs** to correlate results with the JIRA-linked test cases.

* * *

## **Why Manually Created Test Cases Land in “Uploaded Data”**

- **Cause** : When you run tests in Studio and upload results to TestOps, they are treated as **new executions** unless explicitly linked to existing TestOps test cases.
- **Solution** :
  - Use the **`testOpsUpload`** command with the `--testCaseId` parameter to map executions to specific TestOps test cases:

bash

```auto
./katalon -noSplash -runMode=console -projectPath="your.prj" -retry=0 -testSuitePath="Test Suites/your_suite" -browserType="Chrome" -executionProfile="default" -apiKey="YOUR_API_KEY" -testOpsUpload --testCaseId="TEST_OPS_TEST_CASE_ID"

```

- **OR** use Katalon’s **TestOps API** to programmatically link executions.

* * *

## **Mapping Manual Test Cases to JIRA-Linked TestOps Entries**

1. **In Katalon Studio** :

- Ensure the test script includes the JIRA ID in metadata:

groovy

```auto
@Metadata(
  [tags: ["JIRA-ID:YOUR_JIRA_KEY"], 
    customFields: ["JIRA Link": "https://your-jira/browse/YOUR_JIRA_KEY"]
  ]
)

```

1. **In TestOps** :

- Use **JQL** (JIRA Query Language) in TestOps to filter test cases by JIRA ID.
- Configure **Traceability Dashboard** to visualize relationships between JIRA issues and test cases.

* * *

## **Key Benefits of JIRA + TestOps Integration**

1. **Bi-Directional Sync** :

- Update test case statuses in TestOps (Pass/Fail) and reflect them in JIRA issues.

1. **Automated Reporting** :

- TestOps automatically updates JIRA issues with execution summaries.

1. **Prioritization** :

- Identify high-risk JIRA issues by analyzing linked test case failure rates.

* * *

## **Example Workflow**

1. **JIRA** → **TestOps** :

- Generate test cases in JIRA using the Katalon plugin.
- Sync them to TestOps (stored in the “Katalon Cloud” folder).

1. **TestOps** → **Studio** :

- Link TestOps test cases to Studio scripts (via UUIDs).

1. **Studio** → **TestOps** :

- Upload execution results mapped to TestOps/JIRA IDs.

1. **TestOps** → **JIRA** :

- Automatically update JIRA issues with test results.

* * *

## **Troubleshooting Tips**

- **Mismatched Folders** : Use **TestOps Labels** to organize test cases into folders dynamically.
- **Missing Links** : Ensure the JIRA ID is included in both TestOps test case metadata and Studio scripts.
- **API Integration** : Use TestOps REST API to programmatically sync data:

bash

```auto
# Example: Update TestOps test case with JIRA ID
curl -X POST "https://analytics.katalon.com/api/v1/test-cases" -H "Authorization: Bearer $API_KEY" -d '{"name":"Test Case","jiraId":"JIRA-123"}'

```

By properly linking JIRA, TestOps, and Studio, you ensure that every test execution is traceable to its originating requirement.