# Labels

<figure><img src="https://2589376588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOe1Y56Oetn6ATqblYj2K%2Fuploads%2FA3V29SmoGXH7pLJZqLD3%2Fimage.png?alt=media&#x26;token=ef614b7e-bb68-4ad9-8662-c58f783b1bb1" alt=""><figcaption><p>Warp’s issue labels, as seen in a list of open issues.</p></figcaption></figure>

<figure><img src="https://2589376588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOe1Y56Oetn6ATqblYj2K%2Fuploads%2FEHaqLavawvshe2QLLI6w%2Fimage.png?alt=media&#x26;token=83846cd7-81b5-4f80-addf-98bac4fd17c6" alt="" width="375"><figcaption><p>Warp’s issue labels, as seen on an issue’s page.</p></figcaption></figure>

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.
