[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)

# List issues

> Issues filtered by project, assignee, status and tracker, sorted as you ask. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/redmine/list_issues

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)

Issues filtered by project, assignee, status and tracker, sorted as you ask.

Redmine MCP tools: https://cotlet.dev/docs/mcp/redmine.md

MCP tool: `redmine_read → list_issues`

Access: read.

Returns issues with subject, tracker, status, priority, assignee and dates. By default only open issues come back; set status to all or closed to change that. Pages hold up to 100 issues, so read total_count and pass offset for the next page. The project filter takes the numeric project ID.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | no | Only issues of this project (numeric ID from list_projects). |
| `assigned_to_id` | string | no | A user ID, or 'me' for the signed-in account. |
| `status` | string | no | 'open' (default), 'closed', 'all', or a status ID from list_issue_options. |
| `tracker_id` | integer | no | Only issues of this tracker. |
| `sort` | string | no | Column to sort by, e.g. 'updated_on:desc'. Default: Redmine's own order. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `offset` | integer | no | How many items to skip. Use offset + limit while it is below total_count. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "redmine_read",
    "arguments": {
      "operation": "list_issues",
      "arguments": {}
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "issues": [
      {
        "issue_id": 4830,
        "project": "Billing portal",
        "tracker": "Bug",
        "status": "New",
        "priority": "Normal",
        "subject": "Refund email not sent",
        "assigned_to": null,
        "updated_on": "2026-10-16T07:12:00Z"
      },
      {
        "issue_id": 4821,
        "project": "Billing portal",
        "tracker": "Bug",
        "status": "In Progress",
        "priority": "High",
        "subject": "Login loop after password reset",
        "assigned_to": "Dana Whitfield",
        "updated_on": "2026-10-15T14:30:00Z"
      }
    ],
    "total_count": 2,
    "offset": 0,
    "limit": 25
  },
  "isError": false
}
```

Previous: [List issue options](https://cotlet.dev/docs/mcp/redmine/list_issue_options.md)
Next: [Get issue](https://cotlet.dev/docs/mcp/redmine/get_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.