> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/integrations.md). # Integrations ## Integrations Test Manager connects with external systems to keep testing workflows in sync. Integrations support traceability across test cases, requirements, bugs, and external work items. ### Supported integration patterns Current workflows include: * linking external work items to test cases, requirements, and bugs * synchronizing bugs with JIRA * receiving inbound updates from JIRA through webhooks ### JIRA integration JIRA integration keeps bug data aligned between Test Manager and JIRA. When configured: * bugs created in Test Manager create matching JIRA issues * updates in Test Manager update the linked JIRA issue * inbound JIRA webhooks can push updates back to Test Manager Open [JIRA synchronization](/appx_documentation/test-context-manager-documentation/bug-tracking/creating-a-bug/jira-synchronization.md) for the sync workflow. ### Linked work items Linked work items connect product artifacts across systems. You can use them to: * connect requirements to related external issues * connect test cases to planning or delivery work * connect bugs to the broader implementation context This linkage improves reporting and end-to-end traceability. ### Before you configure integrations Confirm these items first: * the target project and issue mappings are defined * the required access and permissions are available * webhook configuration is ready if you need inbound sync ### Where integrations show up in Test Manager Integration data appears in key workflows: * [Bug lifecycle](/appx_documentation/test-context-manager-documentation/bug-tracking/creating-a-bug/bug-lifecycle.md) * [Traceability](/appx_documentation/test-context-manager-documentation/requirements/creating-a-requirement/traceability.md) * [Traceability report](/appx_documentation/test-context-manager-documentation/reports-and-analytics/generating-a-report/traceability-report.md) ### Best practices * keep project mappings stable * sync bugs from execution workflows where context is richest * use linked work items consistently across requirements and defects --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.