> For the complete documentation index, see [llms.txt](https://docs.qyrus.com/device-farm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qyrus.com/device-farm/integrations.md).

# Integrations with Collaboration Tools

Integrating your mobile and web testing workflows with collaboration and project management tools enhances QA productivity, streamlines defect tracking, and facilitates faster bug resolution. Qyrus Device Farm seamlessly connects with Jira to enable one-click bug filing directly from live sessions and test reports.

***

## Why Integrate with Collaboration Tools?

* **Raise Issues Instantly:** Create defects and tasks with attached device screenshots, session metadata, and reproduction steps without leaving Device Farm.
* **Streamline Team Collaboration:** Maintain a unified source of truth in Jira for developers, QA engineers, and product owners.
* **Traceability with Xray & Sub-Tasks:** Link testing issues to existing Jira stories, epics, and Xray test management categories.

> #### [Click here to learn how to configure Jira Integrations in Project Setup](/device-farm/project-creation-and-setup.md#integrations-management)

***

## Utilizing Jira Integration in Device Farm

Jira integration can be invoked from two places:

1. **Inside an Active Testing Session:** Click the **Jira** icon on the device control bar to capture a defect at the exact moment an issue occurs.
2. **From the Test Report:** Review session logs or video recordings post-execution and click the **Jira** icon to file a ticket.

***

## Steps to File a Defect to Jira

1. Click on the **Jira** icon on the control bar or inside the test report.

![Alt text](https://2346916530-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkSZu8cT8D2Zwayrr4I91%2Fuploads%2Fgit-blob-5061aa43e48fd6c4b761ca8a7245936624555b05%2FIntegration-1.png?alt=media)

2. The **Create Ticket** modal will appear with fields populated from your Jira instance:

![Alt text](https://2346916530-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkSZu8cT8D2Zwayrr4I91%2Fuploads%2Fgit-blob-ec70da2b29faf631b889e51cfd3e61dbb3b91aeb%2FIntegration-3.png?alt=media)

### Ticket Form Fields:

* **Select Configuration (Required):** Choose your configured Jira integration from the dropdown.
* **Reporter:** Displays the authenticated user associated with the token.
* **Select Jira Project (Required):** Select the destination Jira project (shows project avatar and key).
* **Issue Type (Required):** Select from supported Jira issue types such as *Bug*, *Task*, *Story*, *Improvement*, or *Sub-task*.
* **Parent Id (for Sub-tasks):** When *Sub-task* is selected, enter the parent issue key (e.g., `PROJ-1234`).
* **Summary (Required):** Enter a clear, concise headline for the ticket.
* **Description (Required):** Provide detailed steps to reproduce, expected results, and observed behavior.
* **Scope of Automation (Xray Integration):** If your project uses Xray, select the automation scope from the configured options.
* **Testcase Category (Xray Integration):** Select the category classification for Xray test management.
* **Priority (Required):** Set the priority level (*Highest*, *High*, *Medium*, *Low*, *Lowest*) with icon indicators.
* **Automatic Attachment:** The current device screenshot and session context are automatically attached to the created Jira issue.

3. Click **“Create Ticket”** to submit. A confirmation notification will display the newly created Jira issue ID and a direct link.

![Alt text](https://2346916530-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkSZu8cT8D2Zwayrr4I91%2Fuploads%2Fgit-blob-f3ea842d6fb2cd28d24a07d614f3e3ff0a248af2%2FIntegration-1.gif?alt=media) ![Alt text](https://2346916530-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkSZu8cT8D2Zwayrr4I91%2Fuploads%2Fgit-blob-7aab33dc3de91f5c410129adb7b704a0364d2abd%2FIntegration-2.gif?alt=media)

***

## Benefits of Qyrus Device Farm Integration

* **Zero Context Switching:** Testers never need to leave the Device Farm workspace to open Jira in another tab, take manual screenshots, or paste device specifications.
* **Rich Diagnostic Context:** Tickets automatically include device OS version, screen resolution, model, session timestamp, and screenshot evidence.
* **End-to-End Traceability:** Keep your development and testing sprints synchronized with real-time updates across Jira and Qyrus.

***