"Unknown tool: update_issue"

[linaia]

Great job with this MCP server for redmine, thank you !

Tested with integration and MCP Inspector , requesting update_issue throws ""Unknown tool: update_issue"" error message

list_projects, list_issues works fine

[yonaka15]

Thank you for the report @linaia !

I've investigated this issue. Redmine provides an API to update issues (PUT /issues/[id].json), so it's feasible to implement the update_issue tool in mcp-server-redmine.

Here's a proposed plan to implement this feature:

1. Define the update_issue tool in the server's tool definitions, specifying parameters like issue_id and fields to be updated (e.g., status_id, priority_id, notes, assigned_to_id).
2. Implement the logic to call Redmine's PUT /issues/[id].json API endpoint.
3. Add appropriate error handling for cases like non-existent issues or permission errors.
4. Test the implementation thoroughly using mcp-inspector.

For testing with mcp-inspector, commands would look something like this (actual parameter names might vary based on implementation):

• To update status and assignee:

  npx -y @modelcontextprotocol/inspector node dist/index.js update_issue --issue_id <your_issue_id> --status_id <target_status_id> --assigned_to_id <target_user_id>
  

• To add a note:

  npx -y @modelcontextprotocol/inspector node dist/index.js update_issue --issue_id <your_issue_id> --notes 'This is an update via MCP.'
  

I will proceed with this plan. I'll create a new task to track the actual implementation of this feature.

[linaia]

I also noticed this could be corrected in src/tools/time_entries.ts : exclusiveMinimum: true -> 0 (should be a Number not boolean)

[gmarquis-sogexia]

I'm also interested by the fix about update_issue :) Thanks in advance !