Redmine AI in your daily work - 5 concrete use cases

You take over an issue three colleagues have worked on. Nobody wants to read everything, and people without context (substitutes, management, new team members) often still don't get the gist.

With the AI Plugin: One click on AI actions in the issue gives you the state in three points: what's the problem, what's been tried, what's still open. The summary appears as a block below the description, on request automatically when the issue is first opened. A second template explains the same content without jargon for non-experts.

The shipped templates (prompts) run with one click, your team needs no specialist knowledge. You can add your own templates for your workflows.

The third follow-up on the same topic, the customer is impatient and so are you. The reply has to be friendly, complete and quick, and it must not promise anything that isn't true.

With the AI Plugin: The AI reply button in the comment toolbar puts a draft into the notes field that knows the issue history. Templates exist for reply draft, follow-up, clarifying questions, documenting the solution and a handover note before your vacation. You change what doesn't fit and save. Nothing goes out without your click.

Plus text correction in every text field: shorten, make formal, simplify for non-experts, translate, make customer-ready. The AI version sits next to the original and is only applied when you want it.

Read more: Draft a customer update from the issues with AI

After the meeting, four tasks sit in a note or an email. Creating each one as an issue means choosing tracker, priority, assignee and writing a description. That tends to get postponed to tomorrow.

With the AI Plugin: The Issue Assistant next to New issue takes the text as it is. It proposes subject, description, tracker, priority and assignee, you say in plain words what should change, and the issue is only created when you click Create issue. Several issues at once are handled by the project's AI Assistant, which shows every change before executing it.

When creating by hand: After ten characters in the subject, the plugin shows similar issues and flags possible duplicates before a second issue for the same problem is born.

Read more: Turn meeting notes into issues with AI

The solution is buried in an issue from two years ago. Full-text search returns 47 results, one of them relevant. Four search terms later you ask colleagues, no one remembers. In the end you write a new answer, possibly different from the old one.

With the AI Assistant: You ask in your project's chat in natural language: How did we solve the login issue at customer A last year? The assistant searches issues and wiki pages of the project and answers with references to the sources, you jump straight to the original.

On every issue page: The plugin shows Similar issues and Related wiki pages, found by meaning rather than wording. So it also finds issues that describe the problem in other words. The same search is built into Redmine's global search. Prerequisite is PostgreSQL, the standard with AlphaNodes hosting.

As self-service in support projects: The person asking can put the same question to the assistant before writing an issue. Colleagues or customers with access to the project describe their request and get the answer from the wiki and from solved issues, with sources. Only if that is not enough does an issue get created. If you run Redmine as a customer system, this gives your customers an answer around the clock, from your own documentation, without anyone sitting in support. The assistant only sees what the person asking is allowed to see.

Every Monday the same routine: export issues, sort in Excel, sum up numbers, write up highlights and risks, copy into Word, send. One hour of work, every week, and the result varies depending on who writes it.

With the AI block on the dashboard: Status report, weekly report or risk overview from the project's current issue data, always in the same format, updated automatically. No copy-paste, no pivot tables.

With many AI services, the processing location, training usage, and third-country data transfer are not clearly defined. From a data protection perspective, these are three open questions that need to be answered before any rollout.

With AlphaNodes AI Hosting (Cloud or InHouse): Arguments your DPO can verify directly:

• Data Processing Agreement under Art. 28 GDPR with AlphaNodes
• Processing in the EU or your own infrastructure
• No training use of your data
• Complete logging of every AI interaction (user, model, prompt, timestamp)
• Redmine permissions also apply to AI access, private comments are never sent

With processing in the EU, the contractual situation and processing location are clearly documented, the third-country question doesn't arise.

Read more: GDPR-compliant AI integration in Redmine