> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/integration.md). # Integration ### **Boost Team Efficiency with JIRA Integration** The User Story Coverage Report integrates seamlessly with JIRA, bringing all your code coverage insights right to your fingertips, without ever leaving your preferred project management system. No more context switching, data hunting, or relying on disparate reports. Here's how it translates to real-world benefits: * **Direct access:** Dive into User Story Coverage data without swapping platforms. View it all right within your preferred project management system, like JIRA. * **Unified Viewpoint:** Embed testing data directly into user stories, ensuring development and QA teams are always on the same page. Streamline processes and eliminate confusion. * **Effortless collaboration:** Break down data silos and promote seamless collaboration. Everyone has access to the insights they need, regardless of their role or project involvement. This fosters a culture of ownership and shared responsibility for code quality. * **Reduced context switching:** Stay focused on what matters - your work. No more jumping between tools to access crucial data. {% hint style="info" %} Connect your JIRA and gain instant insights. Our deployment guide makes it easy! [Deployment Guide](/knowledgebase/guides/user-story-coverage/technical-overview/deployment-guide.md) {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.