Redmine MCP Server

Retrieve the enabled modules for a Redmine project. Modules control which features are visible/usable in a project (e.g., ``issue_tracking``, ``time_tracking``, ``wiki``, ``repository``). Args: project_id: Project identifier (numeric ID or string identifier). Returns: Dictionary with ``project_id``, ``project_name`` and ``enabled_modules`` (list of module name strings). On failure a dict with an ``"error"`` key is returned. Example: >>> await get_project_modules("my-project") { "project_id": 1, "project_name": "My Project", "enabled_modules":…

Backend data source for the project timeline's Refresh button. Returns the same payload as ``show_project_timeline`` without a UI resource; the timeline's iframe calls this over ``tools/call`` with the arguments the view was opened with. Read-only. Args: project_id: The project whose timeline is being refreshed, as a numeric ID or string identifier (e.g. ``1`` or ``"web"``). start_date: Optional window start, ``YYYY-MM-DD``. end_date: Optional window end, ``YYYY-MM-DD``. filters: Optional extra Redmine filter dict, the same shape ``list_redmine_issues`` accept…

Download a Redmine attachment and return a usable reference to it. Downloads the attachment to local disk and returns either an HTTP URL (when the server has a publicly reachable hostname configured) or an absolute local file path (in stdio mode). The caller does not need to know which mode is active. **HTTP mode** (any explicit ``PUBLIC_HOST``, or a non-loopback ``SERVER_HOST``): Returns a dict with ``uri``, ``uri_type: "http"``, filename, content_type, size, expires_at, and attachment_id. An explicit ``PUBLIC_HOST=localhost`` also selects this mode so Docker port-forwarded deployments prod…

Retrieve a specific Redmine issue by ID. Fetch issue details, view a ticket, show a bug report, get issue with comments, journals, attachments, or related metadata. Use this tool to pull a single issue with full context: comments (journals), attachments, custom fields, watchers, relations, subtasks/children, and (when ``REDMINE_AGILE_ENABLED=true``) agile metadata. For listing or filtering across multiple issues see ``list_redmine_issues``; for text search across issues see ``search_redmine_issues``. Args: issue_id: The ID of the issue to retrieve include_journals: Whether to include…

Retrieve one news item, with its comments and attachments. Args: news_id: ID of the news item. include_comments: Include the comment thread (default ``True``). Comments are where a discussion about an announcement lives, so they are on by default -- unlike the issue tools, a news item without them is usually just three fields. include_attachments: Include attachment metadata (default ``True``). Returns: A news dictionary; ``comments`` and ``attachments`` are present only when requested *and* non-empty. On failure, a dict with an ``"error"`` key…

Backend data source for the triage board's Refresh button. Returns the same payload as ``show_triage_board`` without a UI resource; the board's iframe calls this over ``tools/call``. Pass the same arguments the board was opened with, so a refresh redraws the same view. Read-only. Args: project_id: The project whose board is being refreshed, as a numeric ID or string identifier (e.g. ``1`` or ``"testing-project1"``). filters: Optional extra Redmine filter dict, the same shape ``list_redmine_issues`` accepts (e.g. ``{"assigned_to_id": "me"}`` or ``{"trac…

Bulk import multiple time entries in a single call. **Use this tool (NOT ``manage_time_entry(action="create")`` in a loop) whenever the user asks to:** - import a timesheet / weekly timesheet / monthly report - bulk log, batch log, or log multiple entries at once - import several entries, or any list of 2+ time entries - backfill time across many issues or dates - log the same activity for multiple team members at once - log a day's work spanning multiple issues **Prefer this tool over calling ``manage_time_entry(action="create")`` N times** -- it reports partial fail…

List the tags in use on RedmineUP CRM contacts. Use it to discover valid names for the ``tags`` filter of ``manage_contact(action="list")`` and for ``tag_list`` on create/update. Requires ``REDMINE_CRM_ENABLED=true``. Returns: A list of ``{id, name, color}`` ordered by name, or ``{"error": ...}``.

List saved RedmineUP CRM queries for contacts or deals. Saved queries are the named filters users build in the CRM's contact and deal lists. Available with ``REDMINE_CRM_ENABLED`` (``contact``) or ``REDMINE_DEALS_ENABLED`` (``deal``). Args: object_type: ``contact`` or ``deal``. limit: Queries per call, 1 to 100 (default 25). offset: Paging offset (default 0). Returns: A list of ``{id, name, is_public, project_id}`` (``project_id`` is ``None`` for global queries), or ``{"error": ...}``.

List RedmineUP CRM deal statuses, and a project's deal categories. Call this before ``manage_deal(action="create")``, which requires a numeric ``status_id`` and accepts an optional ``category_id``. Requires ``REDMINE_DEALS_ENABLED=true`` and the CRM plugin, Pro edition. Args: project_id: Optional project identifier or id. When given, the project's deal categories are returned as well (categories are defined per project). Returns: ``statuses``: list of ``{id, name, position, is_default, status_type (open|won|lost), status_type_id, color}`` ordered by position…

List all files uploaded to a Redmine project. Returns file metadata (id, filename, size, content type, description, download URL, author, optional version/release) for every file uploaded under Project > Files. Note: This lists files from Redmine's core "Files" module (enabled per project via Settings > Modules > Files). It does NOT list issue attachments (use ``get_redmine_issue`` with ``include_attachments=True`` for those) and does NOT list DMSF documents (pending separate tools). Args: project_id: Project identifier (numeric ID or string identifier). Returns: A list of file met…

List the ids and names of the issue custom fields enabled for a project. Against a stock Redmine only ``id`` and ``name`` carry data. ``field_format``, ``is_required``, ``multiple``, ``default_value``, ``possible_values`` and ``trackers`` come back ``null``, meaning "not readable on this token" -- ``null`` is not ``false`` and not an empty list. In particular ``is_required: null`` does not mean a field is optional, so a create or update can still reject on a field listed here. To set a field, key it in ``fields`` by name or as ``cf_<id>`` with an id from here, or pass ``extra_fields={"custom_…

List members of a Redmine project. Returns all users and groups that are members of the specified project, along with their assigned roles. A role that comes from a group the user belongs to, or from the parent project when this one inherits members, carries ``inherited: true``; Redmine omits the key for a role held directly, and so does this tool -- so test for the key, do not expect ``inherited: false``. A role held both ways appears twice on the same row, once with the key and once without. Args: project_id: Project identifier (ID number or string identifier) Returns: A list of …

List the trackers (issue types) enabled for a specific Redmine project. Unlike ``list_redmine_trackers`` (which returns every tracker defined in the instance), this returns only the trackers available on the given project. Use it to discover valid ``tracker_id`` values before creating an issue in that project. Args: project_id: Project identifier (numeric id or string identifier). Returns: A list of tracker dicts with ``id`` and ``name``. On failure, a list containing a single dict with an ``"error"`` key. Examples: >>> await list_project_trackers("my-project") [{"id": …

List all issue priority levels defined in the Redmine instance. Use this tool to discover valid ``priority_id`` values before calling ``create_redmine_issue`` or ``update_redmine_issue``. Returns: A list of priority dictionaries with ``id``, ``name``, ``active``, and ``is_default``. On failure, a dict with an ``"error"`` key. Example: >>> await list_redmine_issue_priorities() [ {"id": 1, "name": "Low", "active": True, "is_default": False}, {"id": 2, "name": "Normal", "active": True, "is_default": True}, {"id": 3, "name": "High", "active": True, "i…

List all issue statuses defined in the Redmine instance. Use this tool to discover valid ``status_id`` values before calling ``update_redmine_issue``. You can also pass a status name via the ``status_name`` field in ``update_redmine_issue``, which internally resolves the ID. Returns: A list of status dictionaries with ``id``, ``name``, and ``is_closed`` (whether this status counts as "closed"). On failure, a dict with an ``"error"`` key. Example: >>> await list_redmine_issue_statuses() [ {"id": 1, "name": "New", "is_closed": False}, {"id": 2, "name": "In …

List Redmine issues with flexible filtering and pagination support. A general-purpose tool for listing issues from Redmine. Supports filtering by project, status, assignee, tracker, priority, and any other Redmine issue filter. Use this to list all issues in a project, find unassigned issues, or apply any combination of filters. A call with no filter returns the open issues of every project the caller can see, 25 per call, each with its full description. Scope a read with ``project_id`` or another filter, and pass ``fields`` when descriptions are not needed. Args: project_id: Filter by …

List Redmine news (project announcements), newest first. Without ``project_id`` this spans every project the caller can see. Comments and attachments are not included -- the list endpoint does not serve them; use ``get_redmine_news`` for one item's full context. Args: project_id: Restrict to one project (numeric ID or string identifier). Redmine narrows the collection server-side, and answers 404 for a project that does not exist. limit: Maximum news items to return (default 25, max 100). offset: Items to skip, for paging. Returns: A list of news dictionaries…

Lists accessible projects in Redmine. Returns ONLY active projects unless ``filters`` says otherwise. Redmine's ``ProjectQuery`` starts out with a ``status = 1`` filter already set, so a call that passes no ``status`` answers with active projects alone while looking like the whole list. Pass ``filters={"status": "1|5"}`` to get closed projects alongside active ones. ``status`` takes only the ``=`` and ``!`` operators, so ``"*"`` is not a way to ask for every status -- it would be read as a literal value and match nothing. ``filters`` narrows the collection server-side. A filter Redmine canno…

List all saved custom queries visible to the current user. Custom queries are saved issue filters (defined via the Redmine web UI). Once discovered, the ``id`` can be passed to ``list_redmine_issues`` via a ``query_id`` filter to run the query. Note: This tool only READS queries. Redmine's REST API does not support creating, updating, or deleting saved queries. Returns: A list of query dictionaries with ``id``, ``name``, ``is_public``, and ``project_id`` (may be ``None`` for cross-project queries). On failure, a dict with an ``"error"`` key. Example: >>> await list_redm…

List all roles defined in the Redmine instance. Returns basic role metadata (``id`` and ``name``) for every role configured in Redmine. Use this tool BEFORE calling ``add_project_member`` or ``update_project_member`` to discover the correct ``role_ids`` — role IDs vary between Redmine instances and must not be guessed. Returns: A list of role dictionaries, each with ``id`` and ``name``. On failure, a dict with an ``"error"`` key. Example: >>> await list_redmine_roles() [ {"id": 3, "name": "Manager"}, {"id": 4, "name": "Developer"}, {"id": 5, "name": "…

List all trackers (issue types) defined in the Redmine instance. Trackers classify issues (e.g., Bug, Feature, Support). Use this tool to discover valid ``tracker_id`` values before calling ``create_redmine_issue`` or ``update_redmine_issue``. Returns: A list of tracker dictionaries with ``id``, ``name``, and ``description``. On failure, a dict with an ``"error"`` key. Example: >>> await list_redmine_trackers() [ {"id": 1, "name": "Bug", "description": ""}, {"id": 2, "name": "Feature", "description": ""}, {"id": 3, "name": "Support", "description": ""…

List Redmine users with optional filtering. Admin permission is required to list all users. Non-admin users may receive a 403. Use this tool to discover valid user IDs (e.g., for assignment, watchers, or time-entry authoring). Args: name: Optional case-insensitive substring to filter by (matches against login, firstname, lastname, and email). group_id: Optional group ID to filter users who belong to a specific group. limit: Maximum users to return (default 25, max 100). offset: Pagination offset. Default 0. Returns: A list of user dictionaries with ``id``…

List versions (roadmap milestones) for a Redmine project. Args: project_id: The project ID (numeric) or identifier (string). status_filter: Optional filter by version status. Allowed values: open, locked, closed. When None, all versions are returned. Returns: A list of version dictionaries. On failure, a dict with an ``"error"`` key is returned (callers should check ``isinstance(result, dict)`` to distinguish failure from an empty list).

List subtasks (child issues) of a given Redmine issue. Retrieves all issues whose ``parent_issue_id`` equals the given ``issue_id``. To create a new subtask, use ``create_redmine_issue`` with the ``parent_issue_id`` field set. Args: issue_id: ID of the parent issue. Returns: List of child issue dictionaries. On failure a list containing a single dictionary with an ``"error"`` key is returned.

List time entries from Redmine with filtering and pagination. Retrieve time entries with optional filtering by project, issue, user, and date range. Supports pagination for handling large result sets. Args: project_id: Filter by project (ID number or string identifier). issue_id: Filter by issue ID. user_id: Filter by user ID. Accepts a numeric user ID or the literal string ``"me"`` (retrieves the currently authenticated user's entries). Arbitrary strings are rejected at the FastMCP boundary. from_date: Start date filter (YYYY-MM-DD format). to_dat…

List available time entry activities from Redmine. Returns activity types that can be used when creating or updating time entries (e.g., Development, Design, Testing). When called without ``project_id``, returns all global activity types. When called with ``project_id``, returns project-specific activities via ``GET /projects/:id.json?include=time_entry_activities`` (Redmine 3.4.0+). Project-specific IDs differ from global ones — always use project-scoped activities when logging time against a specific project to avoid ``"Activity is not included in the list"`` errors. Args: project_id…

RedmineUP CRM (Contacts) plugin tool. Combined CRUD-by-action. Actions: ``list``, ``get``, ``create``, ``update``, ``delete``, ``assign_to_project``, ``remove_from_project``. Requires ``REDMINE_CRM_ENABLED=true`` and the RedmineUP CRM plugin. One flat signature serves every action, so most parameters apply to some actions and are ignored by the rest. ``search``, ``tags`` and ``assigned_to_id`` narrow a ``list`` on every CRM build. The contact attributes narrow one only on the plugin's Pro build, which registers them as query filters; the Light build registers ``tags`` and nothing else, and…

RedmineUP CRM notes on contacts and deals. Combined CRUD-by-action. Notes are the CRM's activity log ("called them", "sent proposal"). Available when ``REDMINE_CRM_ENABLED`` or ``REDMINE_DEALS_ENABLED`` is set; a note on a deal additionally needs deals enabled and a note on a contact needs CRM enabled. There is no list action: read a parent's notes with ``manage_deal(action="get", include="notes")``. Args: action: ``get``, ``create``, ``update`` or ``delete``. note_id: Required by every action except ``create``. source_type: ``create`` only, required: ``contact`` or ``deal``. …

RedmineUP CRM (Deals) plugin tool. Combined CRUD-by-action. Actions: ``list``, ``get``, ``create``, ``update``, ``delete``. Requires ``REDMINE_DEALS_ENABLED=true`` and the RedmineUP CRM plugin. One flat signature serves every action, so most parameters apply to some actions and are ignored by the rest. Which is which: Args: action: Which operation to run. project_id: On ``list``, restrict to deals in this project. On ``create``, the project to file the new deal under (required). search: ``list`` only. Free-text search over the deal name. status_id: **``list`` return…

List, create, rename, or delete RedmineUP CRM deal categories. Categories are defined per project and referenced by ``category_id`` on deals. Requires ``REDMINE_DEALS_ENABLED=true``; writes need the plugin's ``manage_deals`` permission. Args: action: ``list``, ``create``, ``update`` or ``delete``. project_id: Required for ``list`` and ``create``. category_id: Required for ``update`` and ``delete``. name: Required for ``create`` and ``update``; at most 30 characters and unique within the project. reassign_to_id: ``delete`` only. Category to move the deleted …

Manage DMSF documents (list / get / create / update). Requires the ``redmine_dmsf`` plugin and ``REDMINE_DMSF_ENABLED=true``. Actions: * ``list`` — list documents in a project (or a DMSF folder). * ``get`` — fetch a single document's metadata by ID. * ``create`` — upload a new document. Two-step under the hood: ``POST /uploads.json`` → token, then ``POST /projects/{id}/dmsf/commit.json``. Accepts file content as ``content_base64`` (capped at 50 MiB decoded). DMSF's commit response only …

Read a RedmineUP Helpdesk ticket, or change its customer contact. Actions: ``get`` (read-only) and ``set_contact``. ``get`` returns the Helpdesk data ``get_redmine_issue`` does not carry: the ticket's ``contact`` (``{id, name}``), ``from_address`` (where replies go), ``to_address``, ``cc_address``, ``message_id``, ``source``, ``is_incoming``, ``ticket_date``, the response-time metrics, ``vote``, ``vote_comment`` and ``content`` (the customer's original message). Customer-controlled text is wrapped in boundary tags. ``set_contact`` moves the ticket to another existing contact, given either `…

List, create, update, or delete a Redmine issue category. Args: action: One of: ``list``, ``create``, ``update``, ``delete``. project_id: Project ID or identifier. Required for ``list`` and ``create``. category_id: Category ID. Required for ``update`` and ``delete``. name: Category name. Required for ``create``, optional for ``update`` (cannot be blank). assigned_to_id: Default assignee user ID. Optional for ``create`` and ``update``. reassign_to_id: Reassign existing issues to this category ID on ``delete``. Optional. Returns: ``li…

Edit text or toggle privacy of a Redmine journal (issue note). Both actions are writes and are blocked in read-only mode. Args: action: One of: ``edit``, ``set_private``. journal_id: ID of the journal entry (required for both actions). notes: New notes text for ``edit``; may be an empty string to clear the note. Mutually exclusive with ``notes_upload_id``, and one of the two is required. notes_upload_id: Take the new note from a file staged with ``create_upload_ticket``, decoded as UTF-8. **Prefer this for a long note**: the text travels from d…

List, create, or delete a Redmine issue relation. Args: action: One of: ``list``, ``create``, ``delete``. issue_id: Source issue ID. Required for ``list`` and ``create``. issue_to_id: Target issue ID. Required for ``create``. relation_id: Relation ID. Required for ``delete``. relation_type: One of: ``relates``, ``duplicates``, ``duplicated``, ``blocks``, ``blocked``, ``precedes``, ``follows``, ``copied_to``, ``copied_from``. Defaults to ``relates`` for ``create``. delay: Delay in days for ``precedes`` / ``follows`` relations. Returns: ``lis…

Add or remove a watcher on a Redmine issue. Requires Redmine 2.3.0+. Args: action: One of: ``add``, ``remove``. issue_id: ID of the issue. user_id: ID of the user to add or remove as a watcher. Returns: ``{"success": True, "issue_id": ..., "user_id": ...}`` on success. On error: ``{"error": "..."}``.

RedmineUP Products plugin tool. Combined CRUD-by-action. Actions: ``list``, ``get``, ``create``, ``update``. The plugin exposes no delete endpoint, so there is no ``delete`` action. Requires ``REDMINE_PRODUCTS_ENABLED=true`` and the RedmineUP Products plugin. One flat signature serves every action, so most parameters apply to some actions and are ignored by the rest. The two write actions do not take their payload the same way: ``create`` reads the flat parameters below, while ``update`` reads ``fields`` and ignores every flat one. Args: action: Which operation to run. project_id: O…

Add, update, or remove a Redmine project membership. Args: action: Operation to perform. One of: ``add``, ``update``, ``remove``. project_id: Project ID or identifier. Required for ``action="add"``. membership_id: Membership ID. Required for ``action="update"`` and ``action="remove"``. user_id: User ID. Exactly one of ``user_id`` or ``group_id`` required for ``action="add"``. group_id: Group ID. Exactly one of ``user_id`` or ``group_id`` required for ``action="add"``. role_ids: Non-empty list of role IDs. Required for ``action="add"`` an…

Create or update a Redmine news item (project announcement). Needs a Redmine that exposes the news write endpoint -- core Redmine has since 4.1. A server without it answers with an error rather than silently doing nothing. Deleting is a separate tool, ``delete_redmine_news``, so a deployment can offer announcements without offering their destruction. Args: action: One of ``create``, ``update``. project_id: Project to announce in. Required for ``create``; ignored by ``update``, since news cannot move between projects. news_id: Item to change. Required for ``update``. …

Create a Redmine project, edit its settings, or close and reopen it. Use this tool to set up a new project, rename one, change its description, homepage, parent, visibility, enabled modules, trackers or custom field values, or to close a finished project and reopen it later. A closed project stays visible and readable but accepts no edits. This tool writes the project record itself. Its contents have their own tools: ``manage_redmine_version`` for versions, ``manage_project_member`` for memberships, ``manage_issue_category`` for issue categories. Archiving is not offered. Redmine gates ``ar…

Create, update, or delete a Redmine version (milestone/roadmap entry). Args: action: Operation to perform. One of: ``create``, ``update``, ``delete``. project_id: Project ID or string identifier. Required for ``action="create"``. version_id: Numeric version ID. Required for ``action="update"`` and ``action="delete"``. name: Version name. Required for ``action="create"``, optional for ``action="update"``. description: Version description text. status: Version status. Allowed values: ``open``, ``locked``, ``closed``. Defaults to ``…

List, get, create, update, delete, or rename a Redmine wiki page. Args: action: One of: ``list``, ``get``, ``create``, ``update``, ``delete``, ``rename``. project_id: Project identifier (required for all actions). wiki_page_title: Wiki page title. Required for all actions except ``list``. version: Specific version to retrieve (``get`` only, optional). include_attachments: Include attachment metadata in ``get`` response. Default ``True``. text: Page content. Required for ``create``. Required for ``update`` unless ``uploads`` is given, in …

Create or update a Redmine time entry. Args: action: One of: ``create``, ``update``. hours: Hours spent. Required for ``create``; optional for ``update`` (must be positive if provided). project_id: Project to log against. Required for ``create`` if ``issue_id`` is not provided. issue_id: Issue to log against. Required for ``create`` if ``project_id`` is not provided. user_id: Log on behalf of this user (``create`` only). Requires ``log_time_for_other_users`` permission. time_entry_id: Entry to update. Required for ``update``. activit…

Search for issues, wiki pages and news across the Redmine instance. Args: query: Text to search for. Case sensitivity controlled by server DB config. resources: Filter by resource types. Allowed: ['issues', 'wiki_pages', 'news']. Default: None (searches all three) limit: Maximum number of results to return (max 100) offset: Pagination offset for server-side pagination Returns: Dictionary containing search results, counts, and metadata. On error, returns {"error": "message"}. Note: Only 'issues', 'wiki_pages' and 'news' are supported; Redmine se…

Search Redmine issues matching a query string with pagination support. Performs text search across issues using the Redmine Search API (/search.json), then transparently hydrates the matching ids via /issues.json so structured fields (subject, status, priority, project, assigned_to, author, timestamps) are populated in the response. The follow-up fetch is skipped when ``fields`` only requests id and/or description, which /search.json can serve on its own. Supports server-side pagination to prevent MCP token overflow. Args: query: Text to search for in issues. limit: Maximum number o…

Email a reply to the customer of a Helpdesk ticket. Unlike ``update_redmine_issue(notes=...)``, which only adds an internal journal, this sends ``content`` as an outgoing email to the ticket's requester and records it on the ticket. The email cannot be recalled once sent, so confirm the wording before calling. Works only on a Helpdesk ticket, meaning an issue with a customer attached. The plugin's endpoint checks no project role or permission (per a reading of its 4.2.9 controller in #301), so any authenticated Redmine user can send through it. Requires the RedmineUP Helpdesk plugin and ``R…

Show a live project dashboard (health snapshot) for a project. Use this whenever the user wants an overview, snapshot, health check, or "how is project X doing" view: open vs closed counts, overdue and due-this-week issues, an open-by-priority breakdown, and recent activity. Natural requests include: "how is <project> doing", "show the dashboard for <project>", "project overview / health / status at a glance", or "what needs attention in <project>". Renders an interactive dashboard in clients that support MCP Apps; other clients receive the same structured data. Prefer ``summarize_project_st…

Show a project's schedule as an interactive timeline (Gantt view). Use this when the user wants a timeline, schedule, roadmap, or Gantt view, or asks when a version ships or what is planned over a period: "show the timeline for <project>", "what is the schedule this quarter", "when does v3.0 ship". Issues are drawn as bars from their start and due dates, grouped by target version, with a milestone on each version's due date and a Done section for recently closed work. Renders in clients that support MCP Apps; other clients receive the same structured data. Prefer ``get_gantt_chart`` for raw …

Show a project's issues as a live, interactive board (Kanban view). Use this whenever the user wants to see, view, browse, open, or triage a project's issues visually instead of as a text list. Natural requests that should call this tool include: "show me the board", "open the issue board for <project>", "give me a kanban / board view", "let me see project X's issues", "triage <project>", "what's the status breakdown for <project>", or any ask to display, visualize, or get an overview of a project's issues. Renders the issues grouped into columns by status in clients that support interactive…

Provide a summary of project status based on issue activity over the specified time period. Args: project_id: The ID of the project to summarize days: Number of days to look back for analysis. Defaults to 30. Returns: A dictionary containing project status summary with issue counts, activity metrics, and trends. On error, returns a dictionary with an "error" key.

Update a checklist item's text, done state, or position. Requires the RedmineUP Checklists plugin and ``REDMINE_CHECKLISTS_ENABLED=true``. This is a write operation and is blocked when ``REDMINE_MCP_READ_ONLY=true``. Args: checklist_item_id: The ID of the checklist item to update. subject: New text for the checklist item (optional). is_done: New done state (optional). position: New position/order (optional). Returns: A success dict with the updated fields, or an error dict on failure.

Update an existing Redmine issue. In addition to standard Redmine fields, a ``status_name`` key may be provided in ``fields``. When present and ``status_id`` is not supplied, the function will look up the corresponding status ID and use it for the update. When ``REDMINE_AGILE_ENABLED=true``, RedmineUP Agile fields may also be set: ``story_points``, ``agile_sprint_id`` (set to ``0``/null to remove the issue from its sprint), and ``position`` (also accepted as ``agile_position``). Each may be given top-level in ``fields`` or nested under an ``agile_data_attributes`` dict. They are routed to th…

Upload a file to a Redmine project's Files section. This is the project's document store, not an attachment on something. To attach a file to an issue, pass ``uploads`` to ``create_redmine_issue`` or ``update_redmine_issue``; to a wiki page, to ``manage_redmine_wiki_page``. All three take the same content sources as this tool. **Content sources — provide exactly ONE of:** - ``upload_id``: a file already staged with ``create_upload_ticket``. **The way to send a file that lives on the caller's own machine.** The caller POSTs the bytes to the ticket's ``upload_url`` in one HTTP request, …