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

# Get issue

> One issue with description, history, subtasks, relations and the statuses you may move it to. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/redmine/get_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)

One issue with description, history, subtasks, relations and the statuses you may move it to.

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

MCP tool: `redmine_read → get_issue`

Access: read.

Returns the full issue: description, custom fields, the journal of notes and field changes in order, subtasks, relations and attachments. allowed_statuses lists the statuses your role may set next. Private notes appear only if your role can see them.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `issue_id` | integer | yes | Issue number, e.g. 4821 for #4821. |
| `include` | string | no | Comma-separated extras: journals, children, relations, attachments, watchers, allowed_statuses. Default: all of these. |

## tools/call

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

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "issue_id": 4821,
    "project": "Billing portal",
    "tracker": "Bug",
    "status": "In Progress",
    "priority": "High",
    "subject": "Login loop after password reset",
    "description": "After resetting the password, the login page redirects back to itself.",
    "author": "Tom Becker",
    "assigned_to": "Dana Whitfield",
    "journals": [
      {
        "user": "Tom Becker",
        "created_on": "2026-10-14T09:05:00Z",
        "notes": "Happens in Firefox only.",
        "private": false
      }
    ],
    "children": [],
    "allowed_statuses": [
      {
        "id": 2,
        "name": "In Progress"
      },
      {
        "id": 3,
        "name": "Resolved"
      }
    ]
  },
  "isError": false
}
```

Previous: [List issues](https://cotlet.dev/docs/mcp/redmine/list_issues.md)
Next: [List time entries](https://cotlet.dev/docs/mcp/redmine/list_time_entries.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.