Redmine is used for development work. It is less commonly known as a helpdesk platform but for teams that already run Redmine, adding a support ticket workflow to the same system has a clear advantage: your support team and your development team work in one place, with a direct path from “client reported a bug” to “developer assigned to fix it.”
In practice, the challenge is that native Redmine does not have a helpdesk structure. There is no client-facing ticket submission form, no SLA clock, and no support queue view separate from the development issue list. As a result, support requests end up mixed with development tasks, making it difficult to separate, prioritise, and report on support work independently.
The Redmineflux Help Desk Plugin adds a structured support workflow to Redmine. Clients submit tickets through a web form or by email. Tickets arrive in a dedicated support queue. SLA timers track first response and resolution targets. Support agents manage resolution inside Redmine. When a ticket reveals a bug, the support agent creates a linked development issue in one action.
The short answer: Yes, Redmine can function as a ticketing and helpdesk tool with the Redmineflux Help Desk Plugin. Native Redmine tracks issues but has no client-facing ticket intake, SLA tracking, or support queue. The Help Desk Plugin adds these capabilities directly inside Redmine, so support tickets and development issues share the same system, projects, and reporting without running a separate helpdesk platform.
In fact, many teams run Redmine and a separate helpdesk tool in parallel Freshdesk, Zendesk, or a shared inbox. The problem is that when a support ticket becomes a bug, the information lives in two systems and the handoff is manual. Something always gets lost or delayed in that handoff.
The Redmineflux Help Desk Plugin adds a client-facing ticket submission form. Clients do not need a Redmine account. They submit a request through the web form, and the plugin creates an issue in the designated support project automatically.
Ticket intake can also be configured via email. Redmine parses client emails sent to a designated support address and converts them into issues automatically. The plugin captures the client’s email address and uses it for all follow-up correspondence.
For IT support teams, this replaces a shared inbox with a structured ticket system without requiring clients to learn Redmine.
Support tickets arrive in a queue view separate from the main issue tracker. Support agents see open tickets, their current status, the assigned agent, and the time elapsed since submission in a single view designed for support workflow rather than development issue tracking.
Consequently, the queue separates support work from development work visually. Developers see their issues on the project board or in the issue list. Support agents see their ticket queue. Both views draw from the same underlying Redmine data.
The plugin adds SLA tracking per ticket. SLA rules are configured by the Redmine administrator:
When a ticket is approaching or has exceeded an SLA threshold, the queue view highlights it. Support managers can see at a glance which tickets are at risk and intervene before an SLA breach.
SLA tracking turns support work into a measurable, reportable activity rather than an informal email exchange.
Support managers assign tickets to agents the same way Redmine assigns development issues to developers. Additionally, a queue manager can assign agents manually, or the plugin assigns them automatically via round-robin routing.
When a ticket requires escalation to a senior engineer, to the development team, or to a third party the escalation is recorded as an issue status change with a comment. The escalation path is visible in the ticket history.
When a support ticket reveals a bug, the support agent creates a linked development issue directly from the ticket record. Specifically, the new issue inherits relevant context from the ticket: the problem description, the client’s environment details, and any steps to reproduce captured during support.
The development issue and the support ticket remain linked. When a developer resolves the issue, Redmine notifies the support agent. They can then update the client with the resolution through the same ticket record.
This direct path from client report to development fix without copy-pasting between two systems is the primary reason development-focused teams prefer keeping helpdesk inside Redmine.
The plugin provides support-specific reporting separate from the development issue reports:
Support managers use these reports to assess team capacity, identify recurring issue types, and demonstrate SLA performance to clients.
Want to see the helpdesk workflow in a live Redmine environment? Book a Free Demo 30 minutes covers ticket intake, SLA configuration, and the bug linking workflow.
Software development teams offering client support — teams that build and maintain software for clients frequently have a support obligation alongside active development. As a result, keeping both workflows in Redmine eliminates the overhead of running parallel systems.
IT operations teams — internal IT departments managing infrastructure requests, access provisioning, and system issues benefit from a structured ticket system that connects directly to the issue tracker used for planned IT work.
SaaS and product companies — product teams that handle inbound support from end users can route those tickets to the support queue in Redmine and link recurring issues to the development backlog without a separate integration layer.
Create a Redmine project specifically for support tickets. In this way, support work stays separate from development work at the project level while sharing the same Redmine instance, members, and reporting infrastructure.
Configure the trackers for this project to include a “Support Ticket” tracker with statuses appropriate for support workflows: New, Assigned, Pending Client, Resolved, Closed.
Install the Help Desk Plugin and configure it for the support project:
Define the relationship between the support project and your development projects. When a support agent creates a bug issue from a ticket, specify which development project the issue should land in. This routing ensures bugs from client tickets arrive in the correct development backlog without manual project selection.
Once routing is configured, the path from client report to developer task is automatic.
The Redmineflux In-App Notification Plugin complements the helpdesk workflow. Support agents receive in-app alerts when a ticket is assigned, when a client responds, or when an SLA threshold is approaching without relying solely on email.
For development teams where Redmine is the primary work interface, in-app notifications keep support ticket awareness inside the tool rather than requiring a context switch to email.
Yes. With the Redmineflux Help Desk Plugin, Redmine functions as a full ticketing and helpdesk system. The plugin adds client-facing ticket intake, a dedicated support queue, SLA tracking, agent assignment, and direct bug linking to the development issue tracker all within your existing Redmine instance.
No. The Help Desk Plugin provides a client-facing submission form that does not require a Redmine account. Clients can also submit tickets by sending an email to a designated support address. Redmine creates the ticket automatically and uses the client’s email for follow-up correspondence.
Yes. The Help Desk Plugin includes SLA rules for first response and resolution times. Tickets approaching or exceeding SLA thresholds are highlighted in the support queue. The plugin’s reporting includes SLA compliance rate over a selected period.
Yes. Tickets created by the Help Desk Plugin are Redmine issues they are visible in project reports, can be assigned to members, linked to development issues, logged with time entries, and reported on using standard Redmine reporting tools. The plugin adds a helpdesk layer; it does not replace the underlying Redmine issue system.
The Redmineflux Help Desk Plugin supports Redmine 5.0.x, 5.1.x, and 6.0.x. Teams running earlier versions should contact support before purchasing to confirm compatibility.
A support team running a shared inbox alongside a Redmine development team loses traceability at every handoff. Client tickets that reveal bugs get copy-pasted into Redmine. Bug fixes that resolve client issues never make it back to the ticket record. As a result, the client never gets a proper update. Ultimately, the Help Desk Plugin eliminates these gaps support work and development work share the same system, the same issue records, and the same reporting infrastructure.
