Redmine

Codumentor can talk to your organization's Redmine instance — looking up issues, checking logged time, and creating or updating tickets — without leaving the chat. There is no dedicated Redmine panel; you ask for what you need in plain language and the assistant calls the right tool.

This feature may not be available in all setups. If asking about Redmine issues doesn't work, it may not be enabled by your administrator.

Connecting your account

Redmine tools act as you, using your own Redmine API key — there is no shared instance-wide credential. Before the assistant can look anything up on your behalf:

1. In Redmine, go to My account → API access key and reveal (or generate) your key.
2. In Codumentor, open Settings → User Secrets and add a secret named redmine_api_key (your administrator may have configured a different name) with that value.

If you ask for something Redmine-related before this is set up, the assistant will tell you the key is missing and ask you to add it — it won't retry on its own until you confirm the secret is set.

What you can do

Ask in natural language; the assistant picks the matching action. Typical requests:

"What Redmine issues are assigned to me right now?"

"Show me issue #4213, including its history and attachments."

"How many hours have I logged in Redmine this month?"

"Create a Redmine bug in the Codumentor project titled 'Login fails on Safari' with this description..."

"Add a note to issue #4213 saying the fix is deployed."

"Mark issue #4213 as resolved and assign it to Anna."

Behind these requests, the assistant has access to:

• Searching and reading issues — list or filter issues by project, status, assignee, or a text match, and fetch one issue's full detail (description, history, attachments).
• Listing projects — see which Redmine projects you can access.
• Checking logged time — total or itemized hours by user, project, issue, or date range. This is the only reliable way to answer "how much time did I log this month" — an issue's own hour total is lifetime, not per period.
• Downloading an attachment — pull one of an issue's attachments to a temporary location so the assistant can read or copy it into a repository; its contents aren't pasted into the conversation directly.
• Creating an issue — subject, description, project, tracker, priority, assignee, and any custom fields your Redmine instance defines.
• Updating an issue — status, assignee, subject, description, priority, percent-done, and custom fields.
• Adding a note or comment to an existing issue, optionally marked private.

Looking things up runs immediately, with no prompt. Creating an issue, changing one, or adding a note asks for your approval first, the same way a shell command does.

Subagents get less

If the assistant delegates part of your request to a subagent, that subagent can typically still look up and read Redmine issues, but by default cannot create, update, or comment on one — only the main conversation can do that. Your administrator can change this.

Custom fields and unusual requests

Redmine instances often define custom fields (a "Reporter Email", a priority scheme, a required approval field). Mention them naturally — "file it under the 'Needs QA' custom field" — and the assistant will include them if it can find the corresponding field. For a handful of things with no built-in action (an enumeration list, a saved query), the assistant may fall back to a more generic Redmine request; anything beyond a plain lookup still asks for your approval first.

Limits you should know about

• Only what your Redmine account can already see or do is reachable — the assistant authenticates as you, so it can never read a project or perform an action your own Redmine permissions wouldn't allow.
• An issue's own logged-hours total can't be filtered by date; ask about a specific time range if that's what you need, so the assistant queries time entries directly instead.
• Attachment contents aren't added to the conversation automatically — ask the assistant to read the downloaded copy if you want it discussed.