Open source Redmine plugins

Turn Redmine into a
location-based task manager

The Geo-Task-Tracker (GTT) plugin adds maps, geometry and spatial search to Redmine. Locate issues as points, lines or polygons, see them on a map, and filter them by where they are.

Get started View on GitHub
  • Redmine 6.0 - 7.0
  • PostgreSQL / PostGIS
  • OpenLayers
  • REST API
  • GPLv3
Redmine issue list with an interactive map showing park maintenance issues as points, a line and a polygon

What GTT adds to Redmine

Everything stays plain Redmine: trackers, workflows, permissions and notifications work exactly as before. GTT adds the "where".

Geometry on issues

Attach points, lines or polygons to issues, projects and users. Draw directly on the map or import existing geometry.

Maps everywhere

Issue lists, issue details, project overviews and user profiles all get interactive OpenLayers maps that reflect your filters.

Spatial filters and sorting

Filter issues by map extent or by distance from a location, sort by distance, and show a distance column in the unit you prefer.

Auto-watch nearby issues

Users with a stored location can automatically watch new issues within a chosen distance and get standard Redmine notifications. New in 7.1.

Flexible base layers

Administrators manage map layers for OSM, XYZ, WMS, WMTS and vector tile sources, and projects pick the layers they need.

GeoJSON REST API

The Redmine REST API is extended with GeoJSON geometry and spatial filters, ready for integrations and field data apps.

A closer look

Every issue has a place

Issue pages show the geometry in context, next to the familiar Redmine attributes, watchers and history. Points, lines and polygons are all first-class citizens.

Redmine issue page showing a polygon on a map above the issue attributes

Capture location as you create

The new issue form opens with a map and drawing tools. Click to set a point, draw a line or sketch an area, then fill in the rest like any other Redmine issue.

Redmine new issue form with a map and geometry drawing tools

The plugin family

GTT is modular: start with the core plugin and add what your workflow needs.

redmine_gtt core

The Geo-Task-Tracker plugin: maps, geometry, spatial filters and the extended REST API.

redmine_gtt_fiware

Turn FIWARE context broker notifications (NGSIv2 and NGSI-LD) into geo-referenced issues.

redmine_good_job

Run background jobs in Redmine with GoodJob, backed by your existing PostgreSQL.

redmine_text_blocks

Reply to issues faster with configurable, reusable text blocks.

redmine_gtt_smash

Use the SMASH digital field mapping app for mobile data collection with GTT.

redmine_gtt_print

Print issues with maps as PDF, using Mapfish Print templates.

All repositories

From city sensors to work orders

The redmine_gtt_fiware plugin connects GTT to FIWARE context brokers, in both directions. When an entity changes (a waste container fills up, a sensor crosses a threshold, a citizen files a report), a geo-referenced Redmine issue appears exactly where the work is. And the issues themselves can be published back to the broker, so other systems and organizations see what is being worked on.

An issue appears where the work is

The broker notifies Redmine, and the plugin does the rest: it renders your templates into subject, description and map geometry, groups repeated notifications for the same entity into one issue instead of flooding the tracker, and authenticates every callback with a per-subscription secret.

Redmine issue created from a FIWARE notification, with a map pin at the waste container's location in a park

Subscriptions without writing JSON

Pick a broker connection, say what to watch, and describe the issue with ${...} placeholders. The live preview renders your template against a real entity fetched from the broker, before anything is published.

Subscription form with a live preview of the issue rendered from a sample waste container entity

See who else is on it

Two organizations share a broker, and both track the same overflowing container. Each issue shows the other organization's work order with its status and a link, new issues can be annotated or suppressed while someone else is already on the problem, and foreign status changes arrive as issue notes. Matching uses a small published vocabulary, not a shared database.

Redmine issue whose federation panel lists another organization's work order for the same waste container, with status and a link

Both NGSI standards

Speaks NGSIv2 and NGSI-LD, with the form adapting to whichever the selected broker uses. Verified live against Orion and GeonicDB.

Fits your broker's security

Tokens stored encrypted, relayed per request, or sent browser-direct, in any header your gateway expects: Authorization: Bearer, X-Api-Key, X-Auth-Token.

Issues become entities

Every issue can live on the broker as an NGSI-LD Issue entity with a stable id, kept up to date from creation to closure, so dashboards and other cities' systems see the state of the work without touching Redmine.

redmine_gtt_fiware on GitHub Documentation Vocabulary

Get started

GTT requires Redmine with PostgreSQL/PostGIS. Each release ships a prebuilt archive, so no Node toolchain is needed on the server.

  1. Prepare a PostGIS database

    createdb -U postgres -O redmine redmine
psql -U postgres -d redmine -c "CREATE EXTENSION postgis;"

  2. Install the plugin

    cd /path/to/redmine/plugins
curl -LO https://github.com/gtt-project/redmine_gtt/releases/latest/download/redmine_gtt.tar.gz
tar -xzf redmine_gtt.tar.gz

  3. Migrate and restart

    bundle install
bundle exec rake redmine:plugins:migrate RAILS_ENV=production

Read the getting started guide Releases