Local AI in practice – Redmine ticket analysis with Ollama
After the theoretical exploration of local language models, real practical use now follows: Automatic ticket decomposition using an …
Read articleAt its core, Redmine is a ticket tracker with flexible workflows — open, extensible, and highly customizable.
A “ticket” is not limited to IT incidents. It can represent any work item: a task, request, change, order, service case, or approval step. Each item moves through defined states, responsibilities, and business rules.
In practice, tickets are captured, prioritized, assigned, and processed through a clear workflow. Role and permission models define who can see, edit, approve, or escalate what. Status, deadlines, history, decisions, and communication stay transparent and auditable.
Typical use cases include:
- Project management
- Engineering change processes
- IT service and support
- Order management
- Customer service
- Internal approval and handover workflows
With custom fields, workflow design, and plugins, Redmine can be tailored precisely to your business model — from lean team setups to enterprise-wide process platforms.
For two decades, I have supported organizations in successful Redmine adoption: from reliable operations and system integration to tailored customization and plugin development.
Depending on your constraints, the platform can run as an appliance on bare metal, in virtualized environments, or in cloud-native architectures.
To make Redmine effective in practice, business process consulting is always part of the work: roles, handovers, responsibilities, and workflows are designed so the tool supports the process — not the other way around.