[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create issue

> Create an issue in a project with tracker, subject, description, priority and assignee. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/redmine/create_issue

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Create an issue in a project with tracker, subject, description, priority and assignee.

Redmine API: https://cotlet.dev/docs/api/redmine.md

`POST https://cotlet.dev/api/v1/redmine/projects/{project_id}/issues`

Access: write. Confirm: waits for the user's OK before it runs.

Creates the issue and returns its number and link. The assignee is a user ID from list_project_members; Redmine cannot assign by name. Pass parent_issue_id to make a subtask. Needs the Add Issues permission in your role on the project. The assignee and watchers can be notified according to their notification settings. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Numeric project ID from list_projects. Redmine issue endpoints take the number, not the project identifier. |
| `tracker_id` | integer | yes | Tracker ID from get_project. |
| `subject` | string | yes | Issue title. |
| `description` | string | no | Issue text. |
| `priority_id` | integer | no | Priority ID from list_issue_options. Default: the instance default. |
| `assigned_to_id` | integer | no | User ID from list_project_members. |
| `category_id` | integer | no | Issue category ID from get_project. |
| `parent_issue_id` | integer | no | Number of the parent issue, to create a subtask. |
| `is_private` | boolean | no | true makes the issue private. Default: false. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/redmine/projects/12/issues \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tracker_id":2,"subject":"Fix invoice footer on PDF","description":"From the 14 Oct planning call: the footer overlaps the totals on page 2.","assigned_to_id":31}'
```

**Python**

```python
result = client.call("redmine", "create_issue", {"project_id":12,"tracker_id":2,"subject":"Fix invoice footer on PDF","description":"From the 14 Oct planning call: the footer overlaps the totals on page 2.","assigned_to_id":31})
```

**Node.js**

```js
const result = await cotlet.call('redmine', 'create_issue', {"project_id":12,"tracker_id":2,"subject":"Fix invoice footer on PDF","description":"From the 14 Oct planning call: the footer overlaps the totals on page 2.","assigned_to_id":31});
```

**CLI**

```bash
cotlet call redmine create_issue --data '{"project_id":12,"tracker_id":2,"subject":"Fix invoice footer on PDF","description":"From the 14 Oct planning call: the footer overlaps the totals on page 2.","assigned_to_id":31}'
```

## Example response

```json
{
  "issue_id": 4832,
  "url": "https://redmine.example.com/issues/4832",
  "project": "Billing portal",
  "tracker": "Task",
  "status": "New",
  "priority": "Normal",
  "subject": "Fix invoice footer on PDF",
  "assigned_to": "Priya Nair",
  "author": "Dana Whitfield",
  "created_on": "2026-10-16T09:20:00Z"
}
```

Previous: [List time entries](https://cotlet.dev/docs/api/redmine/list_time_entries.md)
Next: [Update issue](https://cotlet.dev/docs/api/redmine/update_issue.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.