> 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/settings/team/issue-ownership.md).

# Issue ownership

## What is it?

In Swarmia, you can assign issue ownership to a specific team using issue ownership mapping. When looking at a specific team across various views, such as focus summary and investment balance, you'll see a yellow icon indicating issues the team contributed to but doesn't own. You can also toggle "Show only issues owned by team" to hide these cross-team contributions. Work log, on the other hand, shows only issues owned by the team.

## Map issues to teams

When you create a new team, Swarmia automatically suggests a project to map to it. If you have a setup where multiple teams use the same issue tracker project, you can assign the right issues to Swarmia teams based on, e.g., labels or custom fields. Assigning issue ownership for teams is an essential step, as only then will the Jira issues and related data be visible in Swarmia.

[Swarmia issues team settings](https://app.swarmia.com/settings/team/issues)

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-72adb0d306b20431634ef3f8d529708237accc5d%2Fimage.png?alt=media" alt=""><figcaption><p>A project-based issue ownership assignment</p></figcaption></figure>


---

# 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/settings/team/issue-ownership.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.