Download a file attachment from Redmine to the local filesystem. Use redmine_get_issue first to see available attachments and their IDs. Returns the local file path so you can read or process the file.

Get a quick overview of your Redmine workload: issues assigned to you, issues you recently updated, and overdue items. Use this as the first tool when starting a work session to see what needs attention.

Get full details of a Redmine issue including description, metadata, and (by default) all journal updates and attachments. Set include_journals=False for tickets with very long histories that would blow up your context (e.g. recurring incident tickets). Use this to understand the full history of a ticket before updating it.

Search Redmine issues with flexible filters. Filter by project, status, author, assignee, tracker, priority, free-text, and date ranges (created/updated). Supports offset for pagination through total_count. Returns a summary list -- use redmine_get_issue for full details. NOTE: author/assigned_to/updated_by accept 'me' or a numeric user ID -- display names like 'Yuko Matsui' will fail (Redmine API returns 500). Use redmine_find_user to resolve a name to an ID first.

Add a comment/note to an existing Redmine issue. This is the primary way to post updates, progress reports, investigation findings, or review feedback on a ticket. Follow the communication style guide: structured formatting, evidence-based, warm closing.

Edit the text of an existing journal (comment/note) on a Redmine issue. Use redmine_get_issue first to find the journal ID you want to edit. Only the notes text can be changed. Requires Redmine 5.0+.

Create a new Redmine issue. The description should be well-structured: brief statement of what needs to be done, context/why, scope, and links. For bugs: include steps to reproduce, environment, and screenshots.

Update issue fields (status, assignee, priority, due date, etc.) without necessarily adding a note. Use redmine_add_note if you want to post a comment. Use this for pure metadata changes.

List all Redmine projects you have access to, with their identifiers and status.

List all available issue statuses with their IDs. Use this to find the right status_id for updates.

List all available issue trackers with their IDs. Use this to find the right tracker_id.

List all available issue priorities with their IDs.

Search for Redmine users by name. Useful for finding user IDs when assigning issues or @mentioning colleagues.

Find a Redmine user ID by scanning recent issues for matching authors and assignees. Use this as a workaround for /users.json admin restrictions: given a name fragment (e.g. 'Toyoda', 'yoshikuni', 'Murata'), it returns matching user IDs sorted by how often they appear, so the most active match comes first. Once you have an ID, pass it to redmine_search_issues as author/assigned_to/updated_by.

Log time spent on an issue. Include a meaningful comment about what was accomplished during this time.

Get time entries for a user or issue, useful for tracking and reporting.

List all wiki pages in a Redmine project. Returns a hierarchical tree showing page titles, versions, and last-updated dates. Use this to discover available documentation before reading specific pages.

Get the full content of a specific wiki page in a Redmine project. Returns page metadata (author, dates, parent page) and the raw page content (this Redmine instance uses standard Markdown, not textile). Use redmine_list_wiki_pages first to find page titles.