Redmine
Key Info:
Redmine is an open-source web application for multi-project planning, issue tracking, schedules, documents, wikis, time records and role-based collaboration.
Details
Project-management scope
Redmine is a self-hosted, browser-based project management application built with Ruby on Rails. One installation can contain multiple projects, each with its own modules, members and permissions. Core functions include issue tracking, Gantt charts, calendars, roadmaps, time tracking, documents, files, news, forums, wikis and repository integration. The product is open source, so selection should account for both functional fit and the organisation's ability to operate and maintain the chosen deployment.
Evaluation scenario
Create two projects with different teams and visibility rules. Define issue types, statuses, priorities, workflows and custom fields, then import or create a realistic backlog. Assign work across versions, dependencies and milestones. Ask managers to review the roadmap and Gantt view while contributors update issues, attach evidence and record time. Confirm that email notifications and saved queries support the way each role monitors work. Include one external or read-only participant to test whether project boundaries remain clear without granting unnecessary access.
Workflow and reporting
Model one real approval or delivery process rather than accepting the default issue lifecycle. Check which status transitions each role can perform and whether required fields prevent incomplete hand-offs. Test filters, custom queries, calendars, roadmaps and time reports with enough records to expose navigation or reporting limits. If source-code integration matters, connect a test repository and verify that changesets, issue references and access controls behave as expected.
Administration and extensions
Review authentication, role permissions, project templates, backups, upgrades, email delivery and attachment storage with the administrators who will own the service. Redmine supports plugins and themes, but every extension adds compatibility and security work. Establish an approved extension list and rehearse an upgrade using a copy of production data before adopting customisations that are difficult to remove. Document the restore procedure and the ownership of background jobs, mail and file storage.
Decision checkpoint
Measure issue-update effort, reporting accuracy, search success, workflow exceptions and administrative time during the pilot. Confirm the supported Ruby, database and operating environment against current Redmine documentation. Proceed when the configured workflows match actual delivery practices, users can find the records they need, permissions remain understandable, and the operating team can patch, back up and recover the service without relying on undocumented changes.