> For the complete documentation index, see [llms.txt](https://docs.go-atlassian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.go-atlassian.io/jira-software-cloud/teams.md).

# Teams

{% hint style="info" %}
This document refers to Advanced Roadmaps API's, which is a cross-project planning tool only available as part of Jira Software Cloud Premium and Enterprise.
{% endhint %}

{% hint style="warning" %}
This is an experimental API,
{% endhint %}

## Overview

Teams in Advanced Roadmaps are different from the teams found in the rest of Jira Software Cloud. In Advanced Roadmaps, they act as a label applied to issues that designates which team will eventually pick up the work on your timeline. By adding the Team field to your Jira issues, you can save this value back to your Jira issues, which makes sprint planning easier.

<figure><img src="https://4039951191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MRIBKheqm91_IPQsFV_%2Fuploads%2F17kGaqq18YkwKlW4v4FM%2Fimage.png?alt=media&amp;token=81189cb7-a1bd-41e9-8e13-5f37e106116d" alt=""><figcaption></figcaption></figure>

Since Advanced Roadmaps is a planning tool, the Team field is a way to use features like capacity management without assigning issues to individuals, which happens in sprint grooming or planning sessions.

You can also use Advanced Roadmaps' view settings to focus on work assigned to a specific team. **For example**, you can choose to color issues based on the team to which they’re assigned, group issues by team on your timeline, or hide teams from your view.

### Get Teams

`POST /rest/teams/1.0/teams/find`

Gets returns the Teams information from the *Jira Advanced Roadmaps* application.&#x20;

* Teams in Advanced Roadmaps are different from the teams found in the rest of Jira Software Cloud. In Advanced Roadmaps, they act as a label applied to issues that designates which team will eventually pick up the work on your timeline.
* By adding the Team field to your Jira issues, you can save this value back to your Jira issues, which makes sprint planning easier

{% code fullWidth="true" %}

```go
package main

import (
   "context"
   "fmt"
   v2 "github.com/ctreminiom/go-atlassian/v2/jira/v2"
   "log"
   "os"
)

func main() {

   var (
      host  = os.Getenv("HOST")
      mail  = os.Getenv("MAIL")
      token = os.Getenv("TOKEN")
   )

   atlassian, err := v2.New(nil, host)
   if err != nil {
      return
   }

   atlassian.Auth.SetBasicAuth(mail, token)
   atlassian.Auth.SetUserAgent("curl/7.54.0")

   teams, response, err := atlassian.Team.Gets(context.Background(), 1000)
   if err != nil {
      if response != nil {
         log.Println("Response HTTP Response", response.Bytes.String())
      }
      log.Fatal(err)
   }

   log.Println("Response HTTP Code", response.Code)
   log.Println("HTTP Endpoint Used", response.Endpoint)

   for _, team := range teams.Teams {
      fmt.Println(team.Title, team.Id, team.ExternalId, team.Shareable)
   }

   for _, person := range teams.Persons {
      fmt.Println(person.PersonId, person.JiraUser)
   }
}
```

{% endcode %}

### Create Team

`POST /rest/teams/1.0/teams/create`

Create create creates a team on the Advanced Roadmaps.

{% code fullWidth="true" %}

```go
package main

import (
   "context"
   v2 "github.com/ctreminiom/go-atlassian/v2/jira/v2"
   "github.com/ctreminiom/go-atlassian/pkg/infra/models"
   "github.com/davecgh/go-spew/spew"
   "log"
   "os"
)

func main() {

   var (
      host  = os.Getenv("HOST")
      mail  = os.Getenv("MAIL")
      token = os.Getenv("TOKEN")
   )

   atlassian, err := v2.New(nil, host)
   if err != nil {
      return
   }

   atlassian.Auth.SetBasicAuth(mail, token)
   atlassian.Auth.SetUserAgent("curl/7.54.0")

   payload := &models.JiraTeamCreatePayloadScheme{
      Title:     "Team Voldemort",
      Shareable: true,
      Resources: nil,
   }

   team, response, err := atlassian.Team.Create(context.Background(), payload)
   if err != nil {
      if response != nil {
         log.Println("Response HTTP Response", response.Bytes.String())
      }
      log.Fatal(err)
   }

   log.Println("Response HTTP Code", response.Code)
   log.Println("HTTP Endpoint Used", response.Endpoint)

   spew.Dump(team)
}
```

{% endcode %}


---

# 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://docs.go-atlassian.io/jira-software-cloud/teams.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.