> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/modeling-your-deployments/projects/issue-trackers.md). # Issue trackers Once you've [connected your issue tracker](/sleuth-dora/integrations-1/issue-trackers.md), Sleuth will automatically display issues referenced in: * Pull request titles and descriptions * Commit descriptions * Git branch names There are several places in Sleuth where you can view these related issues. At the lowest level, each deploy includes an Issues tab that lists any issues associated with that deploy along with direct links to those issue source records in your issue tracker. ![View of linked issues from the Deploy Details screen](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2Fgit-blob-26b7d5c603ad75cce64bb8fdb24a84f1399f7b9e%2F119fd88%20-%20Sleuth%202021-02-04%2014-52-25.png?alt=media) Sleuth also provides higher-level "Issue breakdowns" on the Project Metrics, Team Metrics, and Work in Progress dashboards, providing visibility into the status and type of any issues referenced across any of the PR/Deploys you have in focus on those dashboards. For Project Metrics and Team Metrics, this means you can see breakdowns for issues you've shipped, while Work-in-Progress displays breakdowns for issues that you're *about* to ship! ![](https://img.announcekit.app/0fe90d6dbe7d996355e2f0ef1e9a5ff9?s=774bde83a95a66fd824e91fc8b09051f) From any of these dashboards, the Issue breakdown chart also provides a clickable drill-through to a detailed listing of issues with links to their source records in your issue tracker.

Drill-through to detailed issue listing from "Issue breakdowns" chart

Issue Type is particularly useful for understanding the nature of the work that's going into each release (new features, bugs, tech debt...), while Issue Status is useful for identifying potential breaks in your issue management workflow (e.g. an issue on the Work in Progress dashboard shows as 'Done' even though it has an outstanding PR). See the p[roject settings details](/sleuth-dora/settings/project/details.md) documentation on how to configure your issue tracker for your project. --- # 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://help.sleuth.io/sleuth-dora/modeling-your-deployments/projects/issue-trackers.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.