Redmine 6.1 – What Actually Changed and Why It Matters

Redmine 6.1 is not a radical redesign. It’s an incremental release with several practical improvements — some visible, some technical.

If you are running Redmine in production, the real question is not whether it’s “exciting,” but whether the changes justify the upgrade effort in your environment.

Below is a straightforward breakdown.

1. Features You’ll Notice Immediately

Reactions on Issues and Notes

Users can now add emoji-style reactions to issues, comments, and forum posts.

What this changes:

• Fewer “+1” comments

• Less notification noise

• Lightweight acknowledgement without adding text clutter

• Slightly more usable async communication for distributed teams

It’s not transformative, but it removes friction. We have upgraded the RedmineX theme and UX Plugin to reflect that.

OAuth 2.0 Provider Support

Redmine can now act as an OAuth 2.0 provider for API authentication.

Why this matters:

• Replaces static API keys

• Enables token-based, revocable access

• Better alignment with modern integrations (CI/CD, BI tools, internal dashboards)

• More secure external API usage

If you integrate Redmine with other systems, this is the most relevant improvement in 6.1.
If you don’t use the API heavily, the impact is minimal.

UX Improvements

Even thought we built the RedmineX theme and UX Plugin around the fact that Redmine is not strong in this department, we like to see improvements in the Default theme as it improves the overall adaptibility of Redmine.

• Sticky headers in long issue views

• One-click copy buttons for API keys and code blocks

• Progress bar custom field for visual tracking

None of these change your workflows.
They reduce minor annoyances.

2. Under the Hood Changes

These are less visible but important for long-term maintainability.

Ruby 3.4 Support (and Dropping Older Versions)

Redmine 6.1 moves forward with newer Ruby versions and drops support for older ones.

Implications:

• Better performance

• Ongoing security support

• Cleaner codebase

• You may need to adjust your server stack if you’re behind

If your infrastructure is already modern, this is straightforward.
If you’re running older OS or Ruby versions, this may require preparation. We're hee to help every stepof the way thanks to your Remote Maintenance service. You give us a clean server, we install & maintain everything for you.

Stimulus.js in Core

Redmine now includes Stimulus.js as part of its frontend foundation.

What this means practically:

• More dynamic UI elements in future releases

• Less reliance on full page reloads

• Cleaner path for modern frontend features

For end users today, the effect is small.
For developers and plugin authors, it’s a step toward a more maintainable frontend architecture.

Bullet Gem Integration

The Bullet gem helps detect inefficient database queries during development.

For end users:

• Better performance at scale over time

For developers:

• Fewer N+1 query problems

• More predictable performance tuning

3. Should You Upgrade?

Ah, the million dollar question. In fact, it's not worth 1 million USD → the Remote maintenance service starts at €1,499.

Upgrade Makes Sense If:

• You use API integrations and want proper OAuth

• You care about staying on supported Ruby versions

• You plan to keep Redmine long-term

• Your plugin ecosystem is compatible

• You want incremental UX improvements without major workflow change

• You run on Redmine 4 or lower (red flag here)

You Might Postpone If:

• You run many custom or legacy plugins not yet tested for 6.1

• Your environment is highly stable and tightly controlled

• The upgrade effort outweighs the functional gain for now

Delaying is not “wrong.”
But postponing multiple major versions usually increases upgrade complexity later.

4. Upgrade Effort: What to Expect

For a standard installation:

• Full database backup

• Plugin compatibility check

• Staging test environment

• Ruby and dependency verification

• Controlled deployment window

For heavily customized instances:

• Custom plugin patching

• UI adjustments

• Post-upgrade performance checks

The effort varies significantly depending on how far you deviated from core Redmine.

5. Where Redmine Is Heading

Redmine 6.1 continues a pattern:

• Incremental UX improvements

• Stronger API security

• Modern Ruby stack

• Gradual frontend modernization

This is evolutionary, not disruptive.

If you treat Redmine as long-term infrastructure, staying within one major version of current releases is generally a safer operational strategy than skipping multiple cycles.

RedmineX Compatibility

From our side:

• All RedmineX plugins are tested for compatibility with 6.1

• We assist with plugin adjustments where needed

• We offer Redmine 6+ as a part of our Remote maintenance service

If you’re running a standard RedmineX stack, upgrading to 6.1 is typically routine.
If your instance is heavily customized, we recommend a structured compatibility review first.

Do You Want a NEW Redmine Experience & Boost Your Productivity?