testeiya 0.2.1 → 0.3.9

package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/index.mdx

@@ -1,98 +0,0 @@
----
-title: Jira Plugin
-description: Learn how to integrate Testomat.io with Jira using the Jira plugin. This guide covers connecting projects, linking/unlinking tests, suites, and plans to Jira issues, running manual or automated tests, managing BDD feature files, attaching test reports, using AI prompts to improve test descriptions, and leveraging the traceability matrix for comprehensive coverage in sprints.
-type: article
-url: https://docs.testomat.io/advanced/jira-plugin
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Jira plugin, Testomat.io, test management, test coverage, BDD, feature files, automated tests, manual tests, Jira integration, traceability matrix, test reporting, AI test descriptions, SSO login
----
-
-import DirectoryLinks from "/src/components/DirectoryLinks.astro";
-
-<DirectoryLinks directory="advanced/jira-plugin" />
-
-The Testomat.io Jira Plugin enhances your Jira experience by enabling you to manage tests directly inside Jira. With this plugin you can:
-
-- Connect multiple Testomat.io and JIRA projects easily
-- Quickly link/unlink tests, suites, and plans to JIRA issues
-- View and edit tests directly in JIRA
-- Use autocomplete and smart suggestions for creating tests
-- Easily modify BDD/Gherkin feature files and scenarios
-- Create multiple tests at once from checklists from bulk create
-- Run manual and automated tests from JIRA tickets
-- Attach test reports to JIRA issues with a click
-- Use tracebility matrix and reports to check test coverage in sprints and project
-- Manage project branches
-- Use AI prompts to generate or improve test descriptions directly in Jira
-
-:::note
-
-Jira Plugin requires an active Jira integration in your Testomat.io project. If Jira is not connected yet, please follow [How to Connect Jira Project](https://docs.testomat.io/integrations/issues-management/jira/#connecting-to-jira-project).
-
-![No linked connection with Jira](./images/att6_401.png)
-
-:::
-
-## How to Use Jira Plugin Without Logging in
-
-When you open a Jira issue with linked Testomat.io items **without logging in**, the visibility depends on the type of **Jira connection** used. For full details on connection types and their permissions, see [Jira connection type](https://docs.testomat.io/integrations/issues-management/jira/#jira-connection-types).
-
-![Jira connection type](./images/att75_401.png)
-
-**Connected with an administrator's account**
-
-You can still:
-
-- View **tests and suites** linked to the issue
-
-![list of tests and suites](./images/gif1_401.gif)
-
-- Browse the **Tests Coverage** screen
-
-![Test Coverage](./images/att7_401.png)
-
-**Connected with a regular account**
-
-- only authorized Testomat.io users will be able to see tests and run results in Jira
-
-## How to Log in to Testomat.io from Jira
-
--To access all Jira Plugin features, you need to log in to Testomat.io. You can log in directly from:
-
-- a Jira issue
-
-![Log In from Jira Plugin](./images/att9_401.png)
-
-- or you can do this from Apps
-
-![Log In from app](./images/att8_401.png)
-
-### Login Options
-
-You can authorize using any of the following methods:
-
-- **Email + Password** — enter your Testomat.io credentials and click **Submit**
-- **Authorize with GitHub** — sign in with your GitHub account
-- **Authorize with Google** — sign in with your Google account
-- **Authorize with SSO** — use your company’s Single Sign-On provider
-
-### What you can do after logging in
-
-Once logged in, you can:
-
-- view linked tests and suites
-- edit them directly in Jira
-- unlink items when needed
-- use AI prompts to enhance test descriptions:
-  - Suggest Description – generate a clear and concise description for a test based on its title and similar tests
-  - Improve Description – refine the existing description to make it clearer
-  - Suggest Better Description – provide an alternative improved description
-
-![Avaliable options](./images/att10_401.png)
-
-## JIRA Plugin Permissions and Security
-
-Testomat.io’s JIRA plugin is designed to integrate seamlessly with your JIRA projects, requiring specific permissions to operate effectively. The plugin has **read access** to all issues of an enabled project to display tests that can be attached to any JIRA issue and can **write properties** to save test data into JIRA storage attached to a specific issue. Importantly, Testomat.io **does not perform any update or delete operations** on your JIRA issues, maintaining the integrity of your project data. The plugin accesses several JIRA API endpoints strictly necessary for its functionality, adhering to high standards of data security and integrity. For detailed information on permissions and security, refer to the [JIRA Permissions](https://docs.testomat.io/legal/security/jira) section in our documentation.

package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/jira-issue.md

@@ -1,151 +0,0 @@
----
-title: Creating Jira Issue
-description: Learn how to integrate Testomat.io with Jira using the Jira plugin. This guide covers connecting Testomat.io projects to Jira, linking/unlinking tests, suites, and test plans to Jira issues, and running manual or automated tests directly from Jira. Manage BDD feature files, attach test reports, and utilize the traceability matrix for comprehensive test coverage in sprints.
-type: article
-url: https://docs.testomat.io/advanced/jira-plugin/jira-issue
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/New_8rxMYOhd_2024-10-19.BaU2EWny_Z1oTGPz.webp
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Jira plugin, Testomat.io, test management, test coverage, BDD, feature files, automated tests, manual tests, Jira integration, traceability matrix, test reporting
----
-
-**Jira integration in Testomat.io** helps QA teams quickly turn test results into actionable bug reports. This feature eliminates the manual effort of copying failed test data into Jira and ensures full traceability between test execution and defect tracking.
-
-With a few clicks, you can:
-
-- **Create a Jira issue** directly from a failed test or run
-- **Link existing Jira issues** to tests or suites
-- **Attach contextual details** (test steps, results, environment, and run links) automatically
-
-This integration was designed to improve collaboration between **QA, development, and management teams**, speeding up feedback loops and ensuring visibility across all project stakeholders.
-
-## How to Create a Jira Issue for a Failed Test
-
-To create a JIRA issue for a Failed Test, open a Run with a failed test. Find a test in list, move the cursor over it and click on the **Link to Issue** icon:
-
-![Testomatio.io - Creating JIRA Issue for Failed Test](./images/New_7T8nObH5_2024-10-19.png)
-
-You can link it to an existing issue **(1)** or create a new one **(2)**.
-
-Once you have decided to create an issue in your Jira project, you can select its ticket types **(3)**.
-
-![Testomatio.io - Link Failed Test to existing issue or create a new one](./images/New_Y2SJbV9K_2024-10-19.png)
-
-You can even create an issue as a subtask by **specifying a Parent ticket**:
-
-![Testomatio.io - Creating JIRA Issue as Subtask](./images/New_8rxMYOhd_2024-10-19.png)
-
-- Once created, the linked issue appears under the test run, indicated by the **issue icon**
-- Hovering over the icon shows the **issue title** and **current status**
-- Clicking the icon redirects to the issue in Jira
-- This icon remains visible both during test execution
-
-![Jira Issue in Ongoing run](./images/att4_462.png)
-
-- and after the run is completed, making it easy to track related issues at a glance
-
-![Completed Run](./images/att5_462.png)
-
-The generated ticket will contain the specified information, as well as information about the test run and a web link to the test run report:
-
-![Testomatio.io - Created ticket in Jira](./images/New_8ENxIFXB_2024-10-19.png)
-
-## How to Create a Jira Issue for a Failed Run
-
-To create a JIRA issue for a Failed Manual or Automated Run, open the run and select the **Link to Issue** option from the dots menu:
-
-![Testomatio.io - Creating JIRA Issue for Failed Run](./images/New_cLq5eNs9_2024-10-19.png)
-
-Create a new issue for a run or append to an existing issue.
-
-![Testomatio.io - Link Failed Run to existing issue or create a new one](./images/New_tYJ8Bm2P_2024-10-19.png)
-
-- Once created, the linked issue appears **under the completed run**, indicated by the **issue icon** in the run’s sidebar
-- Hovering over the icon displays the **issue title** and **current status**
-- Clicking the icon redirects directly to the issue in the Jira project
-
-![Linked Jira to Run](./images/att6_462.png)
-
-## How to Link a Test to a Jira Issue
-
-You can easily connect any individual **test** in Testomat.io to an existing or new Jira issue. This allows quick traceability between your test cases and related Jira tickets.
-
-1. Navigate to the **Tests** page in your Testomat.io project
-2. Open the test you want to link
-3. Click the **extra menu (⋯)** button in the top-right corner
-4. Select **Link to Issue**
-
-![Link to Issue](./images/att41_401.png)
-
-Once the **Link to Issue** modal window appears:
-
-5. To **link to an existing Jira issue**, paste or enter the issue key and click **Link Issue**
-6. To **create a new Jira issue**, click **Create new issue**
-
-![create or link a Jira issue](./images/att42_401.png)
-
-7. Select your **Jira profile** (see details: [Connecting Jira Integration](https://docs.testomat.io/integrations/issues-management/jira/)).
-8. Choose the **Issue Type** from the dropdown (e.g., Bug, Task, Sub-task)
-9. Add a **Title**
-10. Optionally, include a **Description** to provide test context
-11. Fill in any **Jira fields** available in your configuration.
-
-Testomat.io automatically displays all supported fields — such as **Parent**, **Components**, **Fix versions**, **Priority**, **Labels**, or other custom fields defined in your Jira project.
-
-These may appear immediately or after clicking **Show Optional Fields**, depending on your project setup.
-
-:::note
-
-The available fields depend on your Jira project configuration. To see all supported field types in Testomat.io, refer to [Supported Jira Field Types](https://docs.testomat.io/integrations/issues-management/jira/#supported-jira-field-types).
-
-:::
-
-12. Once all required information is filled in, click **Create Jira Issue** to finish linking.
-
-![Save new Jira Issue](./images/att43_401.png)
-
-The linked issue appears under the test, indicated by the **issue icon**, which redirects to the issue in the Jira project. In addition, Testomat.io also displays the linked Jira issue’s **title** and **status**, making it easier to recognize the issue at a glance.
-
-![Linked Jira issue showing title and status](./images/att1_462.png)
-
-:::note
-
-You can link a test to multiple issues. In this case their IDs will be displayed in test view in Testomatio.
-
-:::
-
-![Multiple Jira issues](./images/att2_462.png)
-
-## How to Link a Suite to a Jira Issue
-
-Linking a suite to a Jira issue works similarly to linking an individual test, with one key difference: **all tests within the suite will automatically be linked to the Jira issue.**
-
-:::note
-
-Linking is available only at the **suite level**. You cannot link a Jira issue to a folder, and the **Link to Issue** button does not appear on folder level.
-
-:::
-
-1. Navigate to the **Tests** page in your Testomat.io project
-2. Open the suite you want to link
-3. Click the **extra menu (⋯)** button in the top-right corner
-4. Select **Link to Issue**
-
-![Link Jira Issue to Suite](./images/att45_401.png)
-
-Follow the same steps above as linking a single test: link an existing issue or create a new one, select issue type, fill required fields, and click Create Jira Issue.
-
-When a suite is linked, both the suite and all its tests will display the linked Jira issue icon along with its title and status, providing immediate context.
-
-![Suite Jira Issue](./images/att8_462.png)
-
-:::note
-
-If you unlink a suite from a Jira issue, all its linked tests will be unlinked automatically.
-
-:::

package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/runs-and-reports.md

@@ -1,377 +0,0 @@
----
-title: Runs & Reports in Jira
-description: Learn how to run manual, automated, or mixed test executions in Jira using the Testomat.io plugin. This guide covers configuring advanced settings, executing test runs.
-type: article
-url: https://docs.testomat.io/advanced/jira-plugin/runs-and-reports
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Jira plugin, Testomat.io, test runs, test plan, test execution, manual run, mixed run, automated run, CI/CD, test reports, test analytics
----
-
-With the **Testomat.io plugin in Jira**, your team can efficiently execute and manage test runs directly from Jira. Launch manual, automated, or mixed tests, configure environments and assignees, group related runs, and get a clear overview of all test executions with their current statuses. This integration keeps QA, development, and management aligned, providing full visibility into testing workflows without leaving Jira.
-
-This page explains how to:
-
-- Launch **Manual**, **Mixed**, or **Automated in CI/CD** runs from Jira issues or linked test plans
-- Configure **Advanced Settings** such as environment, assignee (email), RunGroup, CI profiles, and custom parameters
-- Track execution progress and view the current status of each run directly in Jira
-- Receive **Report Notifications** in Jira for failed test runs, with automatically created issues containing detailed run results and optional public report links
-
-## Run Flow
-
-Testomat.io supports three types of test executions **directly in Jira**:
-
-- **Manual Run** - execute tests manually
-- **Automated Run (CI/CD)** - execute automated tests via connected CI service
-- **Mixed Run** - run a combination of manual and automated tests in a single execution
-
-Choose the type of run that fits your workflow and follow the detailed steps below to execute tests directly in Jira.
-
-### How to Launch a Manual Run
-
-Use Manual Run in Jira to execute tests step-by-step directly from the Jira issue. Ideal for fully manual test cases, exploratory testing, or verifying features not yet automated. You can launch a Manual Run in Jira in three different ways:
-
-**Option 1** – From the '...' Menu on the **Tests** Tab
-
-1. Navigate to the **Tests** tab
-2. Click the '...' (extra menu) button on the **Tests** tab
-3. Select **Schedule Run** from the dropdown list
-
-![Schedule Run](./images/att48_401.png)
-
-4. In the **'Select tests to run'** dialog, choose the tests you want to include
-5. (Optional) Enable **Run as Checklist** toggle - if enabled, marks tests to be executed as checklist
-6. (Optional) Enable **Run Automated as Manual** toggle - if enabled, allows automated tests to be executed manually
-
-![Select tests to run](./images/att49_401.png)
-
-7. (Optional) Open the **Advanced settings** to select:
-
-- **Environment** – select where the tests will run (e.g., macOS, Chrome, staging, production)
-- **Assign user** – select the **email of the user added to the project** who is responsible for this run
-- **RunGroup** – optional grouping of related runs for easier tracking and reporting
-- **Title** - provide a descriptive title for the run
-
-8. Click **'Create Run'** to start execution
-
-![Create Run button](./images/att50_401.png)
-
-9. Mark all tests with specific status (e.g., ✔ passed / ✖ failed / ➖ skipped)
-10. Click the **Finish Run** button
-
-![Finish Run](./images/att57_401.png)
-
-**Option 2** – Using the 'Run' Button on the **Tests** Tab
-
-1. Navigate to the **Tests** tab
-2. Click the '✔ Run' button
-3. In the **'Select tests to run'** dialog, choose the tests you want to include
-4. (Optional) Enable **Run as Checklist** toggle - if enabled, marks tests to be executed as checklist
-5. (Optional) Enable **Run Automated as Manual** toggle - if enabled, allows automated tests to be executed manually
-
-![Select tests to run](./images/att51_401.png)
-
-6. (Optional) Use **Advanced settings** to select:
-
-- **Environment** – select where the tests will run (e.g., macOS, Chrome, staging, production)
-- **Assign user** – select the **email of the user added to the project** who is responsible for this run
-- **RunGroup** – optional grouping of related runs for easier tracking and reporting
-- **Title** - provide a descriptive title for the run
-
-7. Click **'Create Run'** to start execution
-
-![Create Run](./images/att52_401.png)
-
-8. Mark all tests with specific status (e.g., ✔ passed / ✖ failed / ➖ skipped)
-9. Click the **Finish Run** button
-
-![Finish Run](./images/att56_401.png)
-
-**Option 3** – From the **'Plans'** Tab
-
-1. Navigate to the **Plans** tab in the Jira issue
-2. Click the **▶︎ icon** (Launch a plan) next to the linked Plan to quickly start a run
-3. or click the **⚙︎ icon** (Launch with advanced options) to configure **Advanced Settings**
-
-![Launch a plan](./images/att53_401.png)
-
-Once the **Manual Run Settings** window opens (this appears only if you clicked the **⚙︎ icon**):
-
-4. (Optional) Enable **Run as Checklist** toggle - if enabled, marks tests to be executed as checklist
-5. (Optional) Enable **Run Automated as Manual** toggle - if enabled, allows automated tests to be executed manually
-
-:::note
-
-**Run Automated as Manual** option is disabled if the selected Plan contains only manual tests.
-
-:::
-
-6. Configure **Advanced Settings**
-
-- **Environment** – select where the tests will run (e.g., macOS, Chrome, staging, production)
-- **Assign user** – select the **email of the user added to the project** who is responsible for this run
-- **RunGroup** – optional grouping of related runs for easier tracking and reporting
-- **Title** - provide a descriptive title for the run
-
-7. Click **'Create Run'** to start execution
-
-![Launch a manual run bia Plan](./images/att61_401.png)
-
-8. Mark all tests with specific status (e.g., ✔ passed / ✖ failed / ➖ skipped)
-9. Click the **Finish Run** button
-
-![Finish Run](./images/att56_401.png)
-
-### How to Launch an Automated Run (CI/CD)
-
-Use Automated Run in Jira to trigger tests automatically via a connected CI/CD service without leaving your Jira issue. Ideal for running regression suites, nightly builds, or executing fully automated test cases directly from the Jira interface.
-
-**Option 1** – From the '...' menu on the **Tests** Tab
-
-1. Click the '...' (extra menu) button on the **Tests** tab
-2. Select **Run in CI** from the dropdown list
-
-![Run in CI](./images/att58_401.png)
-
-:::note
-
-If your CI service is not connected, you will see the message: 'Continuous Integration service is not enabled. Connect a CI service to run automated tests from the Testomat.io Jira Plugin.' To enable CI runs, connect your preferred [CI/CD service](https://docs.testomat.io/integrations/continuous-integration/) in your Testomat.io project settings.
-
-:::
-
-3. Add specific tests to run by selecting one by one or **Select all** option
-
-![Select tests to run](./images/att59_401.png)
-
-4. (Optional) Open the **Advanced settings** to select:
-
-- **Title** - provide a title for the run
-- **CI profile** – select the CI configuration profile for automated test execution
-- **Enter config** – specify custom environment variables (e.g. `ref=main`)
-- **Environment** – select where the tests will run (e.g., macOS, Chrome, staging, production)
-- **Assign user** - select the **email of the user added to the project** who is responsible for this run
-- **RunGroup** - optional grouping of related runs for easier tracking and reporting
-
-5. Click **'Create Run'** to start execution
-
-![Create Automated Run](./images/att60_401.png)
-
-**Option 2** – From the **'Plans'** Tab
-
-1. Navigate to the **Plans** tab in the Jira issue
-2. Click the **▶︎ icon** (Launch a plan) next to the linked Plan **(recommended)** in CI
-3. or click the **⚙︎ icon** (Launch with advanced options)
-
-![Launch a plan](./images/att53_401.png)
-
-4. Once the **Run settings** window opens (this appears only if you clicked the **▶︎ icon**), select:
-
-- **Title** - provide a title for the run
-- **CI profile** – select the CI configuration profile for automated test execution
-- **Enter config** – specify custom environment variables (e.g. `ref=main`)
-- **Environment** – select where the tests will run (e.g., macOS, Chrome, staging, production)
-- **Assign user** – select the **email of the user added to the project** who is responsible for this run
-- **RunGroup** - optional grouping of related runs for easier tracking and reporting
-
-5. Click **'Create Run'** to start execution
-
-![Launch Automated Run](./images/att62_401.png)
-
-6. Once the automated run is created, it appears in the **Runs** tab with the **Pending** status
-
-- The test results will update automatically when your CI job completes — showing the final status
-- No manual action is required in Jira
-
-![CI Run created](./images/att63_401.png)
-
-### How to Launch a Mixed Run
-
-Use Mixed Run in Jira to execute both manual and automated tests in a single run directly from the Jira issue. Ideal when part of the test suite is automated, but some tests still require manual verification. You can launch a Mixed Run in Jira in two different ways:
-
-**Option 1** – From the '...' Menu on the **Tests** Tab
-
-1. Click the '...' (extra menu) button on the **Tests** tab
-2. Select **Mixed Run** from the dropdown list
-
-![Mixed Run option](./images/att64_401.png)
-
-:::note
-
-If your CI service is not connected, you will see the message: 'Continuous Integration service is not enabled. Connect a CI service to run automated tests from the Testomat.io Jira Plugin.' To enable CI runs, connect your preferred [CI/CD service](https://docs.testomat.io/integrations/continuous-integration/) in your Testomat.io project settings.
-
-:::
-
-3. In the **'Select tests to run'** dialog, choose the tests you want to include
-
-![Select mix tests to run](./images/att65_401.png)
-
-4. Configure **Advanced Settings**:
-
-- **Title** - provide a title for the run
-- **CI profile** – select the CI configuration profile for automated test execution
-- **Enter config** – specify custom environment variables (e.g. `ref=main`)
-- **Environment** – select where the tests will run (e.g., macOS, Chrome, staging, production)
-- **Assign user** - select the **email of the user added to the project** who is responsible for this run
-- **RunGroup** - optional grouping of related runs for easier tracking and reporting
-
-5. Click **'Create Run'** to start execution
-
-![Create Run](./images/att66_401.png)
-
-Once the mixed run starts:
-
-6.  **Automated tests** are sent to your connected **CI service** for execution. Their results will update automatically in Jira once the CI job completes.
-7.  **Manual tests** can be executed directly inside Jira — mark each test with its result (e.g., ✔ passed / ✖ failed / ➖ skipped)
-8.  Click the **Finish Run** button to close the run
-
-![Finish mixed run](./images/att67_401.png)
-
-**Option 2** – From the **'Plans'** Tab
-
-1. Navigate to the **Plans** tab in the Jira issue
-2. Click the **▶︎ icon** (Launch a plan) next to the linked Plan
-3. or click the **⚙︎ icon** (Launch with advanced options)
-
-![Launch a plan](./images/att53_401.png)
-
-4. Once the **Run settings** window opens (this appears only if you clicked the **▶︎ icon**), select:
-
-- **Title** - provide a title for the run
-- **CI profile** – select the CI configuration profile for automated test execution
-- **Enter config** – specify custom environment variables (e.g. `ref=main`)
-- **Environment** – select where the tests will run (e.g., macOS, Chrome, staging, production)
-- **Assign user** – select the **email of the user added to the project** who is responsible for this run
-- **RunGroup** - optional grouping of related runs for easier tracking and reporting
-
-5. Click **'Create Run'** to start execution
-
-![Launch Automated Run](./images/att62_401.png)
-
-6.  **Automated tests** are sent to your connected **CI service** for execution. Their results will update automatically in Jira once the CI job completes.
-7.  **Manual tests** can be executed directly inside Jira — mark each test with its result (e.g., ✔ passed / ✖ failed / ➖ skipped)
-8.  Click the **Finish Run** button to close the run
-
-![Finish mixed run](./images/att67_401.png)
-
-## Run Reports in Jira
-
-Once a run is completed, it automatically appears in **Testomat.io** and in the **Runs** tab within Jira. In this tab, you can view all runs that were **launched in Jira** or **linked in Testomat.io project**, and quickly access key information about each run.
-
-- **External link (URL)** – opens the detailed report in Testomat.io
-- **Status icon** – shows the color of the run’s status (Passed / Failed / Skipped)
-- **Title** – the title provided for the run
-- **Run type** – a badge indicating the type of run (e.g., manual / automated / mixed)
-- **Environment** – selected environments for the run (e.g., macOS, Chrome, staging)
-- **Execution date** – date the run was completed (or **Not finished**)
-- **Test statuses** – number of tests with each status (e.g., ✔ Passed / ✖ Failed / ➖ Skipped)
-- **Actions** – **▶︎ icon** appears if the run is not yet completed
-
-![Run general information](./images/att68_401.png)
-
-For full report options (filters, exports, comparisons, etc.), you can **open the Run Reports in Testomat.io**, or to learn more, visit the [Run Reports documentation](https://docs.testomat.io/project/runs/reports/).
-
-### Receive Reports in Jira
-
-You can receive a summary report directly inside Jira by enabling **Report Notifications** in your Testomat.io project settings. This integration automatically posts key information about each test run into your Jira project, including:
-
-- Run ID and Status
-- Project name
-- Number of Executed Tests
-- Execution Date and Duration
-- Failed Tests
-- Environment
-- Link to Full Report
-
-This summary allows you to quickly see the key results of each run directly in Jira, while full details remain accessible via the Testomat.io report link.
-
-![Report Notifications in Jira](./images/att69_401.png)
-
-Learn how to set it up in [Report Notifications in Jira.](https://docs.testomat.io/integrations/report-notifications/jira/)
-
-## Tests Coverage
-
-The Tests Coverage screen provides a traceability matrix showing all Jira issues with their linked
-  tests. For each issue you can see:
-
-  - Title — Jira issue key and name
-  - Tests — number of linked tests
-  - Status — current test run status (e.g., Failed, Passed)
-  - Automation status — percentage of automated tests among linked ones
-
-This gives the team a quick overview of which requirements are covered, how many tests back each issue, and how far automation has progressed per story.
-
-To open the Tests Coverage screen:
-
-1. Open the specific space
-2. Click the 'More' option
-3. Select the 'Tests Coverage' tab
-
-![Tests Coverage tab](./images/att1_575.png)
-
-The automation percentage reflects how many of the linked tests are automated — from 0% (all manual) to 100% (fully automated). Issues with no linked tests signal coverage gaps that need attention.
-
-![Tests Coverage screen](./images/att2_575.png)
-
-## Sprint Coverage
-
-The Sprint Coverage tab gives a high-level summary of test execution health across a sprint. Use it to understand how well a sprint is covered with tests and how the execution is progressing — without leaving Jira.
-
-For each sprint it shows:
-
-- Issues with tests / Issues without tests — how many sprint issues have linked tests and how many are left uncovered
-- Manual tests / Automated tests — breakdown of test types across the sprint
-- Passed / Failed / Skipped / Pending / Not executed — full execution status breakdown
-
-This makes it easy to spot coverage gaps, track automation progress, and assess sprint readiness at a glance.
-
-To check test coverage for a sprint:
-
-1. Open the specific space
-2. Click the 'More' option
-3. Select the 'Sprints Coverage' tab
-
-![Sprint Coverage](./images/att3_575.png)
-
-4. Enter the sprint ID(s)
-5. Click the 'Submit' button
-
-![Search sprint ID(s)](./images/att4_575.png)
-
-:::note
-
-To find your sprint ID, visit the [Jira Software sprint ID guide](https://support.atlassian.com/jira/kb/jira-software-how-to-identify-the-id-of-a-sprint/).
-
-:::
-
-## Data Sync in Jira
-
-Testomat.io and Jira are continuously synchronized to ensure test data stays up to date across both systems. This **two-way sync** keeps all team members — QA, development, management, and stakeholders — aligned.
-
-**Automatic Sync**
-
-All key updates are automatically synchronized:
-
-- Linked test cases, test suites, and plans remain aligned in both systems
-- Statuses of linked Jira issues are synchronized
-- Executing a run in Testomat.io updates the corresponding Jira issue with the latest run status
-- Launching or updating a run from Jira instantly reflects in Testomat.io
-- Testomat.io settings — including environments, branches, users, run groups, and CI integrations — are synchronized and visible in Jira
-
-This real-time, two-way sync ensures that everyone sees the same up-to-date information, eliminating confusion and reducing manual updates.
-
-**Manual Sync**
-
-If your Jira issue view or run list does not show the latest data, you can trigger synchronization manually. This ensures that all test results, linked issues, and run information are up-to-date in both Jira and Testomat.io.
-
-To manually refresh data:
-
-1. Open the **Tests** tab in the Jira issue
-2. Click the '⋯' (extra menu) button
-3. Select **Sync** from the dropdown list
-
-![Sync button](./images/att55_401.png)
-
-Testomat.io will re-fetch the latest information and update linked test results, statuses, and settings inside Jira. This keeps your Jira and Testomat.io data fully consistent — whether you rely on automatic background sync or perform a quick manual refresh when needed.
-