DleJTicket gives your site a full ticket desk without leaving Joomla: users submit and reply to tickets from the frontend, staff manage them from a normal Joomla admin list, and every reply and notification runs through Joomla's own systems — its Mail Templates, its permissions, its scheduled tasks — rather than a private layer bolted on top. Two packages are built and tested separately, one for Joomla 4 and one for Joomla 5/6, so you install the one that matches your site rather than one bundle papering over both.

Tickets that behave like tickets

Each ticket carries a status, a priority, an assigned owner, and a full message thread. Staff and requester replies are visually distinct, attachments are supported per message, and internal notes let staff talk to each other on a ticket without the requester ever seeing them.

Real Joomla mail, not a private mailer

Notification emails run through Joomla's own Mail Templates system (System → Mail Templates), so they're editable, translatable, and consistent with however the rest of the site sends mail — not a separate templating layer you have to learn on top of it.

Answer by email, not just by logging in

An optional scheduled task can poll a support mailbox and drop replies straight onto the matching ticket, so staff and requesters can keep a conversation going from their inbox. This needs a mailbox that supports plus-addressing and, on PHP 8.4 and later, the IMAP extension installed separately — both covered in Email Reply to Ticket.

Custom fields, your way

Add text, list, or checkbox fields to the ticket form from the admin, and they show up automatically on every ticket — no template overrides required.

Answers that don't get asked twice

Any ticket can be converted into a Knowledge Base article from the admin. Each message becomes its own attributed block in the article rather than one run-on paragraph, and internal notes are never included — only what the requester actually saw.

Bring your data with you

Import and export tickets, replies, and custom field values as CSV/JSON, so migrating onto — or off of — another ticket system doesn't mean starting from zero.