No description
- Python 98.9%
- Dockerfile 1.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
claude
682257937b
Redmine returns 2xx for a PUT that silently drops a field it won't apply -- most commonly status_id, when the target status isn't reachable from the issue's current status under that tracker's workflow (no error, no journal entry). Observed live against Redmine issue #9 in the "Claude Projekt" project: update_issue(status_id=4) ("Wartend") reported "Issue #9 updated." from status "Neu", but the status stayed "Neu" -- only routing through the allowed intermediate status "In Arbeit" actually worked. update_issue now re-reads the issue after writing and compares every requested status_id/due_date/assigned_to_id/tracker_id/priority_id against what actually landed, so a caller (human or agent) doesn't trust a success message that didn't do anything. See also the project-doc writeup in claude/redmine-mcp-findings.md (REDMINE-Test project) for the full repro. |
||
| Containerfile | ||
| oauth.py | ||
| requirements.txt | ||
| server.py | ||