Redmine 7 explained - what's new and should you upgrade?

Twenty years after the first Redmine release, version 7.0 is finally out.

Whenever a major Redmine version appears, a couple of questions immediately follow:

• Is there anything users will actually notice?

• Is there any reason for the infrastructure team to care?

• And most importantly: Is it worth upgrading from version 5&6?

Many articles simply list every new feature. That isn't particularly useful because not every improvement has the same impact. Some changes you'll appreciate every day. Others matter only if you're responsible for maintaining the server.

Let's separate them.

Redmine 7 User Interface: What's Changed?

Theme and Navigation Get a Cleaner Layout

One of the most visible changes is the addon of ther user and project menus.

User-related actions are now grouped under a dedicated profile menu instead of being spread across the header. The menu is opened by clicking your avatar—or your initials if no avatar is configured.

The change itself isn't revolutionary, but after using it for a while the old layout suddenly feels dated.

One thing worth mentioning is that the menu is intentionally minimal. Users coming from our UX Plugin may notice that features such as condensed layout, super condensed mode or dark mode are still outside of Redmine core—and honestly that's probably the right decision. Those are theme preferences rather than universally accepted defaults.

The project menu got revamped too and feels more up-to-date.

Relevant changes:

• https://www.redmine.org/projects/redmine/repository/revisions/master/changes?rev=31353

• https://www.redmine.org/issues/31353

Preview Redmine files without downloading everything

This is one of those improvements that sounds small but saves time every single day. By default, Redmine 7 can preview PDFs and common image formats including JPG and AVIF directly in the browser. Administrators can also enable previews for Microsoft Office (.docx, .xlsx, .pptx) and LibreOffice Writer (.odt) documents by installing Pandoc, allowing users to inspect document contents without downloading them.

If you've ever downloaded ten attachments just to find the correct specification, you'll appreciate this immediately.

Interesting changes:

• PDF preview (#22483)

• Office preview (#8959)

• SVG preview (#44126)

• AVIF preview (#43943)

Editing markdown is a little better

Nobody upgrades because of editor improvements.

But once they're there, you quickly stop wanting to live without them.
Two particularly welcome additions are:

• pasting spreadsheet ranges directly into wiki tables

• proper Tab / Shift+Tab indentation in CommonMark lists

Neither changes your life, but both remove tiny daily annoyances. If you prefer Markdown, the editing experience is now noticeably smoother. If you rely on a full-featured WYSIWYG editor, CKEditor still remains the more capable option.

Redmine 7 productivity improvements

Redmine 7 also introduces dozens of smaller enhancements that won't make release headlines but collectively improve everyday work.

Some examples:

• automatic watchers for assignees

• relative default due dates

• easier bulk exports

• improved assignee selection for larger organizations

None of these justify the upgrade alone, but together they make Redmine feel more polished.

Redmine 7 webhooks: the biggest architectural change

If I had to choose a single feature that changes Redmine's future, it wouldn't be any UI improvement. It would be native webhooks.

For years Redmine has mostly been a system that waits for somebody to ask it for data. Webhooks finally allow Redmine to push information the moment something changes.

That opens the door for:

• AI knowledge base synchronization

• Slack notifications

• Microsoft Teams automation

• CI/CD workflows

• ERP integrations

• event-driven architectures instead of endless polling

For companies building automation around Redmine, this is probably the most important feature of the entire release.

Rails 8 and Ruby 4 are a bigger deal than they look

From an administrator's perspective, Redmine 7 is much more than a UI update.
It moves the entire platform onto:

• Rails 8

• Ruby 4

That means newer dependencies, better long-term support and removal of several aging components.

Among others:

• Raphael.js disappears

• HTML sanitization moves to Loofah

• numerous internal libraries are modernized

Users won't notice, but somewhere in the server room a nocturnal creature known as the sysadmin will silently celebrate.

Security quietly gets better

Redmine 7 also improves several areas that most users never see.
Two worth mentioning:

• Sudo Mode is now enabled by default

• API keys now record their last usage

Neither sounds exciting. Both make life considerably easier when you're responsible for security audits.

Looking ahead: gemified plugins

One feature many plugin developers are still waiting for is support for gemified plugins. The feature is currently targeted for Redmine 7.1 and should simplify dependency management and plugin installation for developers.

For most Redmine administrators and end users, however, this isn't a deciding factor when planning a Redmine 7 migration

Should you upgrade to Redmine 7?

That's the million-dollar question.

Our recommendation is usually conservative. At RedmineX, we rarely jump on a major Redmine release immediately. The reason is simple: a production Redmine installation is rarely just Redmine. It's an ecosystem of carefully selected community and commercial plugins, and every plugin developer needs time to validate compatibility with the new platform.

If you're running a vanilla Redmine installation, upgrading to Redmine 7 is a straightforward decision. If your instance relies on a larger plugin stack, patience often pays off. We'd recommend evaluating Redmine 7 in a test environment during 2026 while waiting for your plugin ecosystem to fully catch up.

In our experience, a smooth upgrade that preserves every feature your users rely on is far more valuable than being the first to run the latest version.

RedmineX PRO tip

Every Redmine upgrade eventually becomes a plugin compatibility project rather than a Redmine project.

That's usually where most of the work goes.

Before scheduling any migration we always recommend checking:

• Ruby compatibility

• Rails compatibility

• third-party plugins

• custom patches

• database backup strategy

Only then does the Redmine upgrade itself become the easy part.

Upgrade to Redmine 7 without downtime, broken plugins or late-night debugging.