Redmine

Redmine expert Agile¶

Agile boards for Redmine: a Kanban/Scrum board built on Redmine's own query system, story points, sprints with a backlog planner, and charts.

The board is a Redmine query. Every filter, column, grouping and visibility rule you already use on the issue list applies to a board unchanged, and a saved board is a single row in Redmine's queries table — the plugin adds no query schema of its own.

Features¶

• Board — columns from issue statuses, drag & drop, swimlanes, advisory WIP limits, configurable card fields, sub-columns from a shared Prefix: status naming, and saved boards.
• Story points — stored per issue, offered as a configurable value list (modified Fibonacci by default), restrictable to selected trackers, and available as a sortable column and filter on the issue list.
• Sprints — a first-class entity with start and end dates, an open/active/closed lifecycle, and Version-style sharing across a project tree. Redmine versions remain usable for planning alongside sprints.
• Backlog planner — drag issues into sprints or versions from a dedicated planning view, with the same filters and card fields as the board plus saved backlogs, behind its own project module.
• Charts — burndown, burnup, cumulative flow, velocity and cycle time, in issues, hours or story points.
• Colours — cards coloured by tracker, priority, status, project, assignee, spent time, or per issue.
• REST API — read and write agile data (story points, sprint assignment), plus full sprint CRUD.

Design notes¶

A few deliberate choices, because they affect correctness rather than taste:

• Board ranks are fractional and computed on the server. A move sends only the dragged card and its two neighbours, and writes one row once the cards around it carry ranks. Re-indexing a whole column in the browser loses concurrent moves and silently reorders cards that are paginated out of view.
• Chart history is reconstructed in a single pass over one journal query and cached, rather than re-scanning every issue's journals once per date.
• No inline JavaScript. Views render markup; data reaches the browser through a JSON island. The board works under a script-src 'self' content security policy.
• No global monkeypatching of ActiveRecord::Base or ApplicationController.

Requirements¶

• Redmine 5.0 or newer (tested against 5.1, 6.0, 6.1 and 7.0)
• Ruby 3.2+ / MySQL, MariaDB or PostgreSQL
• No additional gems — Chart.js is vendored with the plugin

Links¶

• Source and issue tracker
• Changelog
• REST API reference

Licensed under the GPL-2.0-or-later. This is an independent, clean-room implementation and contains no code from any other agile plugin.

Installation¶

1. Copy the plugin into your Redmine's plugins directory:
   

   cd /path/to/redmine/plugins
   git clone https://github.com/expertZentrale/redmine_expert_agile.git
   

   
   Or unpack a release archive from the Releases page into plugins/. The archive already contains a top-level redmine_expert_agile/ directory.
2. Run the plugin migrations:
   

   cd /path/to/redmine
   bundle exec rake redmine:plugins:migrate NAME=redmine_expert_agile RAILS_ENV=production
   

3. Restart Redmine.
4. Enable the expert Agile module per project under Project settings → Modules. Enable expert Agile Backlog as well if you want the backlog planner.
5. Grant the permissions your roles need under Administration → Roles and permissions.

No additional gems are required. Chart.js ships with the plugin, so there is no dependency on any other plugin's assets.

Upgrading¶

Re-run the migration step after replacing the plugin directory, then restart. Migrations are numbered and additive; none is ever edited after release.

Permissions¶

Saving a backlog uses the two board permissions above, which belong to the expert Agile module. A project that enables expert Agile Backlog on its own can therefore filter its backlog but not save one — enable both modules if saved backlogs are wanted.

Configuration¶

Administration → Plugins → Redmine expert Agile. Every setting ships with a default, so a fresh install is usable immediately. Two worth knowing:

• Board item limit (default 500) caps how many issues one board render loads. A board that hits the cap says so rather than looking complete.
• Chart item limit (default 1000) and chart cache duration (default 60 minutes) bound the cost of the charts that replay issue history. The counting charts are not subject to the cap.

Card colours for trackers, priorities and statuses are managed under Administration → Agile card colors.

Running alongside RedmineUP Agile¶

All classes, tables and routes are prefixed, so both plugins can be installed at the same time. However, both patch Issue, IssueQuery and ProjectsHelper, so enabling both on the same project is not supported. Migrate a project by disabling one module and enabling the other.