Redmine is a general-purpose issue tracker, which is its strength and the reason it needs explaining. These pages show what it looks like configured for four specific kinds of work, and which features are doing the actual work in each.
Issue tracking, sprints and releases, repository integration, and the migration path off per-seat tooling.
Change history you can hand to an auditor, role-based access that survives review, EU or US residency, and the security questionnaire.
Non-conformance and corrective-action tracking, multi-site structure, supplier coordination, and a usable interface for non-developers.
Asynchronous status without another meeting: daily digests, saved queries, chat integrations and time zones that behave.
Most project tools arrive with somebody else's process baked in and a settings page that lets you change the colors. Redmine arrives with almost nothing decided. Trackers, statuses, workflows, roles, permissions, custom fields and project structure are all yours to define, which means a Redmine configured for a software release train and a Redmine configured for a factory's corrective-action process barely look like the same application. That flexibility is why Redmine is still in service after twenty years, and it is also why “what does it do” is a hard question to answer in one paragraph. So we have answered it four times instead, each around a real workflow rather than a feature list.
Flat pricing. $24/mo for up to 25 users, $49/mo for up to 100, $169/mo for up to 250. Unlimited projects on every plan. Nothing on this site is priced per seat, so adding the people who need read access does not change the bill. Pricing.
Full administrator access. Every plan, from Startup. You configure trackers, workflows, roles and fields yourself, and you can install plugins. This is what makes the four configurations possible in the first place.
Managed infrastructure. Redmine version upgrades, operating system and stack patching, backups with point-in-time recovery, TLS, scaling and disaster recovery are ours. What we manage.
A way in and a way out. Moving from Jira, self-hosted Redmine or another host starts with a free assessment; the migration itself is quoted after it. And you can request your full database and files at any time and self-host. Migration.
Each one is organized the same way and answers the same three questions in that industry's terms: what the recurring workflow is, which Redmine features carry it, and where the configuration effort actually goes. None of them is a feature list, because a feature list does not tell you whether the tool fits. A note on effort, since it is the part vendors leave out: Redmine rewards configuration and punishes defaults. A team that spends a day defining trackers, required fields, per-role transitions and three or four saved public queries gets a system people use without training. A team that turns it on and hands out the URL gets an abandoned issue list. That day of work is the same on every host; what differs is whether you are also maintaining the server underneath it.
If your industry is not one of the four, that is not a signal about fit. It is a signal that we have not yet written a page we would stand behind for it. Redmine runs in healthcare, education, construction, government, agencies and research; we would rather publish four pages built on real workflows than twelve built on a template. If you want to know how it maps to your work, ask — you will get an answer from someone who has configured it.