> 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-agile/boards/backlog.md).
# Backlog
In Jira, a backlog is a prioritized list of work items that need to be completed. It serves as a repository for all the tasks, user stories, bugs, and other work items that are yet to be worked on or are in the planning stage. Backlogs are typically associated with agile project management methodologies such as Scrum and Kanban.
Backlogs are visualized as lists of items that can be sorted, filtered, and prioritized. Teams can easily move items between different backlogs, update their status, estimate effort, and collaborate on the work items. Backlogs provide a centralized view of all the work in progress and assist in effective planning, tracking, and delivery of projects.
### Move issues to backlog
`POST /rest/agile/1.0/backlog/issue`
Move moves issues to the backlog.
* This operation is equivalent to remove future and active sprints from a given set of issues.
* At most 50 issues may be moved at once.
### Move issues to a board backlog
`POST /rest/agile/1.0/backlog/{boardId}/issue`
* This operation is equivalent to remove future and active sprints from a given set of issues if the board has sprints.
* If the board does not have sprints this will put the issues back into the backlog from the board.
* At most 50 issues may be moved at once.
{% code fullWidth="true" %}
```go
package main
import (
"context"
"github.com/ctreminiom/go-atlassian/jira/agile"
"github.com/ctreminiom/go-atlassian/pkg/infra/models"
"log"
"os"
)
func main() {
var (
host = os.Getenv("HOST")
mail = os.Getenv("MAIL")
token = os.Getenv("TOKEN")
)
agile, err := agile.New(nil, host)
if err != nil {
return
}
agile.Auth.SetBasicAuth(mail, token)
agile.Auth.SetUserAgent("curl/7.54.0")
payload := &models.BoardBacklogPayloadScheme{
Issues: []string{"KP-23"},
RankBeforeIssue: "",
RankAfterIssue: "",
RankCustomFieldId: 0,
}
response, err := agile.Backlog.MoveTo(context.Background(), 5, payload)
if err != nil {
if response != nil {
log.Println("Response HTTP Response", response.Bytes.String())
log.Println("Status HTTP Response", response.Status)
}
log.Fatal(err)
}
log.Println("Response HTTP Code", response.Code)
log.Println("HTTP Endpoint Used", response.Endpoint)
return
}
```
{% 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-agile/boards/backlog.md?ask=&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.
