> ## Documentation Index
> Fetch the complete documentation index at: https://kb.packfiles.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Labels

> These help keep your migration projects organized.

<Frame caption="Warp’s issue labels, as seen in a list of open issues.">
  <img src="https://mintcdn.com/packfiles/Jt8JnIIrXRnRUKLp/content/media/images/image%20(55).png?fit=max&auto=format&n=Jt8JnIIrXRnRUKLp&q=85&s=83b1f7df3b440be9acab9472b5aff114" alt="" width="1938" height="470" data-path="content/media/images/image (55).png" />
</Frame>

<Frame caption="Warp’s issue labels, as seen on an issue’s page.">
  <img src="https://mintcdn.com/packfiles/Jt8JnIIrXRnRUKLp/content/media/images/image%20(56).png?fit=max&auto=format&n=Jt8JnIIrXRnRUKLp&q=85&s=057babb7aa0b5261c8d9b1d9b431d0c3" alt="" width="375" data-path="content/media/images/image (56).png" />
</Frame>

Warp automatically generates four labels for each issue it creates, which specify:

1. The repository’s **source organization**. In the examples above, the source organization is **joey-ado-testing** in Azure DevOps.
2. The repository’s **source team**. In the examples above, the source team is **first project** in Azure DevOps.
3. The repository’s **source**. In the examples above, the source is Azure DevOps.
4. The repository’s **activity**. In the examples above, the repository is inactive.

In addition to the labels that Warp automatically generates for issues, you can also assign your own labels to any issue.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.