> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/data-model/entities/issues.md).

# Issues

Issues from your issue trackers, and the projects, sprints, and initiatives that organize them.

Issues from your issue trackers, and the projects, sprints, and initiatives that organize them.

* [Initiative](/data-model/entities/issues/initiative.md) — Initiatives are high-level goals that group related issues together. They can be managed in Swarmia, or synced from issue trackers like Jira or Linear.
* [Issue](/data-model/entities/issues/issue.md) — Issues represent work items in your issue tracker (such as Jira, Linear, etc.).
* [Issue custom field](/data-model/entities/issues/issue-custom-field.md) — Definition for the custom field.
* [Issue custom field value](/data-model/entities/issues/issue-custom-field-value.md) — Value of a custom field for an issue.
* [Issue source installation](/data-model/entities/issues/issue-source-installation.md) — Issue tracker instances used by the organization (such as Jira, Linear, etc.).
* [Issue sprint period](/data-model/entities/issues/issue-sprint-period.md) — Represents an issue that was part of a sprint.
* [Issue status period](/data-model/entities/issues/issue-status-period.md) — Represents the time periods an issue has spent in a specific status.
* [Issue status transition](/data-model/entities/issues/issue-status-transition.md) — One row per issue and ordered pair of source statuses the issue moved between directly. Jira only, as Swarmia builds status periods from the Jira status changelog.
* [Issue time in status](/data-model/entities/issues/issue-time-in-status.md) — One row per issue and source status, rolling up every separate visit the issue made to that status. Jira only, as Swarmia builds status periods from the Jira status changelog.
* [Jira issue link](/data-model/entities/issues/jira-issue-link.md) — Directed link between two Jira issues — e.g. "blocks", "duplicates", or "belongs to". It reads as a sentence: "{outward issue} {outward phrase} {inward issue}", e.g. "PROJ-1 blocks PROJ-2".
* [Project](/data-model/entities/issues/project.md) — Projects from issue trackers like Jira, Linear, etc.
* [Sprint](/data-model/entities/issues/sprint.md) — Sprints represent time-boxed iterations in your issue tracker (Jira, Linear, etc.).

{% hint style="info" %}
This page is automatically generated
{% 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://help.swarmia.com/data-model/entities/issues.md?ask=<question>&goal=<user_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.