expert for Redmine Deutsch

Open source · GPL-2.0 · Redmine 5.1 to 7.0

Redmine, with the parts we kept wishing it had

An email helpdesk with SLA tracking, agile boards built on Redmine's own query system, Prometheus metrics, and attachment previews. Built at expert for the Redmine we run ourselves, released under the same licence as Redmine.

Each of these started as something missing from our own installation. They are separate plugins — install one, or all four. None of them phones home, none needs a licence key, and none holds your data anywhere but in your own Redmine database.

  • expert Helpdesk

    Mailboxes become a helpdesk. Incoming mail turns into a ticket, replies land on the ticket that already exists, and agents answer the customer without leaving Redmine. SLA, contacts and phishing detection on top.

    v0.24.2
  • expert Agile

    A Kanban and Scrum board that is a Redmine query — every filter and column you already use applies unchanged. Story points, sprints, a backlog planner and five kinds of chart.

    v0.10.2
  • expert Metrics

    Answers "can I restart Redmine right now?" — who is active, on an admin page and as Prometheus metrics on /metrics, with a Grafana dashboard. No configuration, no permissions.

    v1.6.1
  • expert Lightbox

    Click an image or a PDF attachment and it opens in a modal instead of navigating away. Native browser dialog, no jQuery, no third-party libraries.

    v1.3.0

Four plugins, one set of rules

We wrote these for a Redmine that people at expert use every day, which is the only reason they look the way they do. The constraints we set ourselves are worth knowing before you install anything:

  • The same licence as Redmine. GPL v2 or later, because a Redmine plugin is loaded into the Redmine process and patches its classes — it is a derivative work, and we treat it as one. No per-server fee, no licence key, no tier that unlocks the feature you actually wanted.
  • Tested against every supported Redmine. The suites run on Redmine 5.1, 6.0, 6.1 and 7.0 on every push, and each plugin is additionally booted inside the official redmine Docker images for the same versions.
  • Nothing is fetched at runtime. No CDN, no external font, no analytics beacon. Chart.js is vendored into the plugins that draw charts, and Agile vendors the Coloris colour picker; everything else is the Ruby standard library and what Redmine already ships.
  • Optional means off. The AI features, the knowledge base and the phishing check all ship disabled. Turning one on is a deliberate act, and each one fails closed — a broken model response never mails your customer.
  • Seven languages in the UI, two in the docs. Every plugin speaks English, German, Spanish, French, Italian and Portuguese (Portugal and Brazil); READMEs, changelogs and screenshots come in English and German.

Also from us: python-redmine-expert

For scripts and integrations that talk to Redmine from Python, we maintain python-redmine-expert, a fork of Maxim Tepkeev’s Python-Redmine. Development of the original has stopped, so we picked it up; the vast majority of the code is still his. The import name stays redminelib, so it is a drop-in replacement for python-redmine 2.5.

  • Up to Redmine 7.0. The REST API additions of Redmine 6.0 to 7.0, including OAuth2 access tokens, on Python 3.10 to 3.14 and PyPy3.
  • The RedmineUP plugins, no Pro Edition needed. CRM, Helpdesk, Agile, Checklists and Questions. RedmineUP support used to be part of the paid Pro Edition; we wrote it anew, following the Pro Edition’s API where it had one, so code written for it keeps working. The Pro Edition’s own code is not part of the fork.
  • Our own plugins. Resources for the REST APIs of expert Helpdesk and expert Agile.
  • The original’s licence. Apache 2.0. Install it from the GitHub releases; the documentation covers every resource.

Testers wanted

Try it, break it, tell us

These plugins are young and move quickly. The suites run on every Redmine from 5.1 to 7.0, but our own installation is only one setup — we would like to hear from people who run them somewhere else: another mail server, another theme, next to other plugins, or with a workflow we never thought of. Something broken, something missing, something that works but feels wrong: all of it helps.

Pick a plugin:

The bug form asks for the plugin version and your environment; pasting the table from Administration → Information covers the rest. To hear about new versions, watch the repository on GitHub for releases.

Latest release

Compatibility →