No — it's an optional companion extension, not a dependency. It's a convenient modal login for a module position, useful because submitting a ticket requires being logged in, but the component works with any login method already on your site.

Whichever matches your site. The two are built and released separately rather than as one bundle covering both; installing the wrong one fails Joomla's compatibility check rather than partially installing.

The link is released automatically. The source ticket goes back to offering "Convert to KB" instead of pointing at an article that no longer exists.

Not currently. Priority is set once by the requester at submission and there's no admin control to change it afterward — only status (Open, Pending, Resolved, Closed) can be updated from the ticket view.

Not directly. Import/Export is built around DleJTicket's own data — Tickets, Knowledge Base articles, and Messages, exported as CSV or JSON and matched back by ticket number or ID on re-import. It's meant for backing up your own data or moving it between two DleJTicket installs, not for migrating from a different product's format.

If the site uses JCE as its editor, its Front End profile needs to include the groups submitting tickets, or the editor area renders empty. TinyMCE and CodeMirror don't need this — it's specific to JCE's profile-based permission system, not something DleJTicket controls.

They need the `core.manage` permission for the component. It does double duty — it's the normal "can access the backend" permission, but on the frontend ticket list it's also what turns on the manager view: seeing every requester's tickets and filtering by user, instead of only their own.

Joomla's Mail Style defaults to Plain Text, and DleJTicket's templates are built HTML-first. Set Mail Style to **Both** under Global Configuration → Mail — this sends the styled HTML version with a plain-text fallback, so it looks right in both kinds of mail client.

No. It's an optional feature. Users can always reply by logging in and using the ticket page directly; email reply is a convenience on top of that, not a requirement.

Yes, for everything except email reply. On PHP 8.3 and earlier, the IMAP extension needed for reply-by-email ships with PHP and just needs enabling in `php.ini`. On PHP 8.4, IMAP was removed from PHP core entirely and moved to PECL — it needs `pecl install imap` run separately, which many shared hosts won't offer. If it's unavailable, the mail check task reports exit code 5 and logs the reason rather than breaking anything else. Every other part of the component — tickets, replies, the Knowledge Base, custom fields — is unaffected either way.