---
title: "Move issues to epic"
method: POST
path: "/rest/agile/1.0/epic/{epicIdOrKey}/issue"
tags: ["Epic"]
---

# Move issues to epic

`POST /rest/agile/1.0/epic/{epicIdOrKey}/issue`

Moves issues to an epic, for a given epic id. Issues can be only in a single epic at the same time. That means that already assigned issues to an epic, will not be assigned to the previous epic anymore. The user needs to have the edit issue permission for all issue they want to move and to the epic. The maximum number of issues that can be moved in one operation is 50. **Note:** This operation does not work for epics in next-gen projects.

## Path parameters

- `epicIdOrKey` string, required

## Request body

- object
  - `issues` string[]

## Response `204`

Empty response is returned if operation was successful.

## Other responses

- `400` — Returned if the request is invalid.
- `401` — Returned if the user is not logged in.
- `403` — Returned if the user does not have a valid license or does not have edit issue permission for all issues to assign or for the epic.
- `404` — Returned if the epic does not exist or the user does not have permission to view it.

---

[API](https://skmtc.net/atlassian/apis/jira-software-cloud-api.md) · [All operations](https://skmtc.net/atlassian/apis/jira-software-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/jira-software-cloud-api/revisions/4e108d54b990/schema)