Jira Project versions API

This resource represents project versions. Use it to get, get lists of, create, update, move, merge, and delete project versions. This resource also provides counts of issues by version.

Operations 15

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /rest/api/3/project/{projectIdOrKey}/version Page through a project's versions · Get project versions paginated #
Ask an LLM
“Can I search a project's versions by name and filter to released or archived ones?”
“Which versions in a project are still unreleased, sorted by release date?”
Tell an agent
List versions in project {projectIdOrKey} page by page.
Find {status} versions in project {projectIdOrKey} whose name contains {query}.
GET /rest/api/3/project/{projectIdOrKey}/versions Get all versions of a project unpaginated · Get project versions #
Ask an LLM
“Can I get every version of a project in one unpaginated response?”
“What's the full release list for a project?”
Tell an agent
Get the complete, unpaginated version list for project {projectIdOrKey}.
Return all of project {projectIdOrKey}'s versions in a single call.
POST /rest/api/3/version Create a project version · Create version #
Ask an LLM
“How do I add a new release version to a project?”
“Can I set start and release dates when creating a version?”
Tell an agent
Create version {name} in project {projectId}.
Create version {name} for project {projectId} releasing on {releaseDate}.
DELETE /rest/api/3/version/{id} Delete a version (legacy) · Delete version #
Ask an LLM
“Can I delete a version and move its fix-version issues somewhere else using the older delete endpoint?”
“What happens to issues when a version is deleted with the deprecated method?”
Tell an agent destructive · confirm first
Delete version {id} with the legacy delete endpoint.
Delete version {id} and move its fix issues to version {moveFixIssuesTo}.
GET /rest/api/3/version/{id} Get a project version · Get version #
Ask an LLM
“What are the dates and release status of a particular version?”
“Can I look up one version by its ID?”
Tell an agent
Get version {id}.
Show release details for version {id}.
PUT /rest/api/3/version/{id} Update or release a project version · Update version #
Ask an LLM
“Can I mark an existing version as released?”
“Is it possible to rename a version or change its release date after creating it?”
Tell an agent
Mark version {id} as released.
Rename version {id} to {name} and set its release date to {releaseDate}.
PUT /rest/api/3/version/{id}/mergeto/{moveIssuesTo} Merge one version into another · Merge versions #
Ask an LLM
“Can I merge two versions so all fix-version references point at one?”
“What happens to the source version when versions are merged?”
Tell an agent destructive · confirm first
Merge version {id} into version {moveIssuesTo}.
Fold duplicate version {id} into {moveIssuesTo} and delete it.
POST /rest/api/3/version/{id}/move Reorder a version in a project · Move version #
Ask an LLM
“Can I change the display order of versions in a project?”
“Is there a way to move a version to the top of the list?”
Tell an agent
Move version {id} to position {position}.
Place version {id} right after version {after}.
GET /rest/api/3/version/{id}/relatedIssueCounts Count issues that reference a version · Get version's related issues count #
Ask an LLM
“How many issues use a version as their fix version or affected version?”
“Before deleting a version, can I see how many issues reference it?”
Tell an agent
Count the issues related to version {id}.
Show fix-version and affected-version issue counts for version {id}.
GET /rest/api/3/version/{id}/relatedwork List related work on a version · Get related work #
Ask an LLM
“What related work items, like design docs or links, are attached to a version?”
“Can I see a release's related work links?”
Tell an agent
List related work for version {id}.
Show the links attached as related work to version {id}.
POST /rest/api/3/version/{id}/relatedwork Add a related work link to a version · Create related work #
Ask an LLM
“Can I attach a new link, like release notes, as related work on a version?”
“What category is required when adding related work to a release?”
Tell an agent
Add related work {title} at {url} to version {id} under category {category}.
Link {url} to version {id} as {category} related work.
PUT /rest/api/3/version/{id}/relatedwork Update a related work link on a version · Update related work #
Ask an LLM
“Can I change the title or URL of an existing related work link on a version?”
“Which kinds of related work can be edited through the API?”
Tell an agent
Update related work {relatedWorkId} on version {id} to point at {url}.
Rename related work {relatedWorkId} on version {id} to {title} in category {category}.
POST /rest/api/3/version/{id}/removeAndSwap Delete a version and swap in replacements · Delete and replace version #
Ask an LLM
“Can I delete a version and reassign its fix and affected issues to other versions?”
“Does deleting a version also update version custom fields on issues?”
Tell an agent destructive · confirm first
Delete and replace version {id}, swapping its fix-version issues onto {moveFixIssuesTo}.
Remove version {id}, replacing affected-version references with {moveAffectedIssuesTo}.
GET /rest/api/3/version/{id}/unresolvedIssueCount Count unresolved issues in a version · Get version's unresolved issues count #
Ask an LLM
“How many issues in a release are still unresolved?”
“Is a version ready to ship, or does it still have open issues?”
Tell an agent
Count the unresolved issues in version {id}.
Show total versus unresolved issue counts for version {id}.
DELETE /rest/api/3/version/{versionId}/relatedwork/{relatedWorkId} Remove a related work link from a version · Delete related work #
Ask an LLM
“Can I delete a related work item from a release?”
“What permissions are needed to remove related work from a version?”
Tell an agent destructive · confirm first
Delete related work {relatedWorkId} from version {versionId}.
Remove the related work link {relatedWorkId} on version {versionId}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/jira:jira-project-versions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

jira-project-versions-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  contact:
    email: ecosystem@atlassian.com
  description: Jira Cloud platform REST API documentation
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  termsOfService: https://developer.atlassian.com/platform/marketplace/atlassian-developer-terms/
  title: Jira Cloud platform REST Project versions API
  version: 1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df
servers:
- url: https://your-domain.atlassian.net
tags:


# --- truncated at 32 KB (75 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-project-versions-api-openapi.yml