---
ref: tool:atlassian/create-jira-work-item
name: Create a Jira work item
company: company:atlassian
workflows: []
access: [mcp, cli, api]
tags: [capability:manage-tasks, category:project-management, has:api, has:cli, has:mcp]
docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post
updated: 2026-09-27
---

# Create a Jira work item

Creates a Jira work item (an issue) in a project with its type, summary, description, assignee and labels, and returns its key.

Note: The fields a work item accepts depend on its project and type: read them first with `GET /rest/api/3/issue/createmeta/{projectIdOrKey}/issuetypes`. On the API, `description` must be Atlassian Document Format.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v2/mcp" } } }
```

Call the MCP tool `createJiraIssue`.

Server URL: https://mcp.atlassian.com/v2/mcp

Note: Tools beyond the listed ones are found with `discover` and run with `executeRead` or `executeWrite`; some spend Rovo credits.

### CLI (official)

Install the command and sign in with it, then confirm it runs.

```sh
brew tap atlassian/homebrew-acli && brew install acli
acli --version
```

Run `acli jira workitem create`.

Note: Sign in with `acli jira auth login --web`. The CLI covers Jira only.

### API (official)

- Base URL: https://{site}.atlassian.net
- Endpoint: `POST /rest/api/3/issue`
- Auth: send the header `Authorization: Basic $ATLASSIAN_API_KEY`
- Get a key: https://id.atlassian.com/manage-profile/security/api-tokens
- Docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

Note: `{site}` is your Atlassian site name, as in `acme.atlassian.net`. `ATLASSIAN_API_KEY` holds the base64 of `<email>:<api token>`, and Confluence paths start with `/wiki`.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.